Introduction
| Excerpt |
|---|
This guide provides defintions and explanations for all of the components required to build and |
...
publish Logica applications. |
Overview
The HSPC The Logica development efforts exists to fulfill the mission of HSPCLogica: "Improve health by creating a vibrant, open ecosystem of interoperable platforms, applications, and knowledge assets. The various systems, technologies, tools, and applications created by HSPC by Logica exist to enable the ecosystem."
...
Logica Sandbox
The HSPC The Logica Sandbox is the heart of the HSPC the Logica ecosystem. The HSPC The Logica Sandbox is a place where a developer can build and test apps according to standards that allow the apps to be fully compatible with production systems from Healthcare industry leaders. The HSPC The Logica Sandbox provides EHR simulation, tools, and data to enable a user or a team of users to quickly bring an app to production.
...
Logica Platform
The HSPC The Logica Platform are the backend systems that enable the HSPC the Logica Sandbox and support the FHIR and SMART on FHIR specifications. The HSPC The Logica Platform uses technologies such as MySQL, HAPI FHIR, JPA, OpenID Connect, OAuth2, Java, HTML, and JavaScript to build authentication servers, resource servers, messaging servers, and reference applications. The HSPC The Logica Platform artifacts are open source. A developer that is interested in platform components may host and extend HSPC extend Logica Platform artifacts. A developer that is interested in app development should use the HSPC the Logica Sandbox and the hosted HSPC hosted Logica Platform components found there.
...
- The app registering with the EHR
- The EHR presenting the app as a link or icon within the EHR that the practitioner can open
- The app receiving a launch request from the EHR containing the location of the EHR FHIR resource server
- The app following the OAuth process for receiving authorization for the EHR FHIR resource server.
- The app querying data from the EHR FHIR resource server.
Most of the tools and sample apps produced by HSPC by Logica are SMART on FHIR apps.
HL7 FHIR
For an application or system to be HSPC be Logica compatible it must use HL7 FHIR to exchange data. FHIR describes an object model, a messaging payload, and an API. FHIR users resources to model clinical and administrative concepts, profiles for semantic interoperability, and RESTful HTTP networking protocol. FHIR modeling efforts try to model the most common 80% of real-world object models as representations in FHIR Resources. To accommodate the less common 20%, FHIR Resources offer extension mechanisms.
...
Syntactic interoperability refers to the ability of separate systems to use a common representation for structure. HSPC achieves Logica achieves syntactic interoperability using FHIR Resources. An example of syntactic interoperability is where two systems agree that a "patient" has a "first name" that is a xs:string and a "date of birth" that is a xs:date. Syntactic interoperability is the first level of interoperability.
...
Semantic interoperability refers to the ability of separate systems to understand each other. Semantic interoperability is buildt upon syntactic interoperability. HSPC achieves Logica achieves semantic interoperability using FHIR Profiles. An example of semantic interoperability is where two systems agree that a "patient" with a coded value for "ethnicity" will use the HL7 codes for ethnicity (http://www.hl7.org/fhir/v3/Ethnicity/index.html). There is a lot of modeling activity around different profiling efforts. Profiles that are known to the HL7 FHIR community can be found on the Profiles tab of the Resource definition (http://www.hl7.org/fhir/observation-profiles.html).
...