Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Travis Cummings: This should read as a guide that refers to the reference.  The purpose of this is to put all of those things together.  Also, add an intro section to this, and every other guide.

HL7 FHIR

HL7 FHIR is the choice of HSPC for interoperable system communication.  For an application or system to be HSPC compatible it must use 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 non-common 20%, FHIR Resources offer extension mechanisms.

Syntactic Interoperability

Syntactic interoperability refers to the ability of separate systems to use a common representation for structure.  HSPC 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

Semantic interoperability refers to the ability of separate systems to understand each other.  Semantic interoperability is build upon syntactic interoperability.  HSPC 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 (ex: http://www.hl7.org/fhir/observation-profiles.html).

Detailed Clinical Models

From wiki.hl7.org: Detailed Clinical Models (DCM) are descriptions of items of clinical information that include the clinical knowledge on the concept, the data specification, a model and where possible, technical implementation specifications. A DCM is a conceptual specification of the semantics of discrete structured clinical information. It provides the data elements and attributes, including the possible values and types of the attributes, needed to convey the clinical reality in a fashion that is understandable to both clinical domain experts and modelers.

Medical Terminology

<>

SMART on FHIR

OAuth 2

<>

OpenID

<>

Launch Context

<>

  • No labels