Page Comparison

Introduction

...

...

Tiers

Clinical and Administrative Applications

HSPC compliant Logica compliant applications use standards defined by the SMART on FHIR specification for authentication, authorization, and launch context. These applications can be embedded in the EHR workflow by launching from within the EHR, or may run as a pre-authorized backend service. See App Developer's Guide for JavaScript and Java Client examples. HSPC compliant applications use FHIR for semantically interoperable data exchange.

...

Logica and SMART Client Libraries

HSPC provides Logica provides a Java Client library for the SMART specification, and the SMART team provides JavaScript, Python, and iOS client libraries.  In addition, FHIR defines a REST API for resource operations.

...

Logica Compliant Platform

An HSPC compliant Logica compliant platform is an EHR that supports technologies chosen by HSPCLogica.  These technologies include:

• SMART on FHIR for authentication, authorization, and launch context
• HTTPS for transport
• REST for FHIR resource API
• JSON for transport serialization (in favor of XML)
• FHIR terminology specification for medical encoding
• JWT for credentials

FHIR enabled proprietary EHR systems

Proprietary EHR systems are able to be HSPC compliant by providing authentication and authorization from the SMART on FHIR specification and resources by the FHIR specification.  Our HSPC Logica Reference Implementation is a fully functional example of an HSPC compliant EHR that may be used as a test system for application developers, or may be used as an example for EHR platform developers.  Our HSPC Reference Implementation provides an authorization server and a resource server together on the same Apache Tomcat instance, but co-resident deployment is not required for an EHR. 

Industry Standards

The HSPC has identified industry standards that are to be used for HSPC compliant platforms and applications.

...