interoperable-health-data-model
Service icon

Interoperable Health Data Model

Stable version 2.0.0 (Compatible with OutSystems 11)
Uploaded
 on 26 Feb
 by 
KRE8 IT
5.0
 (1 rating)
interoperable-health-data-model

Interoperable Health Data Model

Details
The Interoperable Health Data Model helps OutSystems developers build digital health applications that are ready for interoperability when needed, without having to deal with the complexities of the HL7 FHIR standard.
Read more

The Interoperable Health Data Model includes data structures and lists of valid options that have been designed to be compatible with the HL7 FHIR R4 standard.


The included data structures are:

  • Simpler than the HL7 FHIR data structures.
  • Easier to understand and easier to work with, ensuring rapid development for digital health solutions.
  • Great starting point for digital health solutions because they include all the standard data elements required for future healthcare interoperability.
  • Can be translated to and from HL7 FHIR Resources when full interoperability is needed.


The included options lists are:

  • Simple to use in your application, because they are returned as DropdownOption lists based on the OutSystems UI data structure.
  • Pre-populated (bootstrapped) with codes from HL7 FHIR value sets to ensure that the data used in the provided data structures contain valid values.
  • Exposed as attribute specific Service Actions (e.g. Patient_GenderIdentities) to make it easier to return the relevant list of options.
  • Can be translated to and from HL7 FHIR Terminology Codings or Codeable Concepts when full interoperability is needed.


When you are ready to make your application fully interoperable, we offer two options to help with this:

  1. Healthcare Interoperability Components for OutSystems - for those who would like to integrate these into their OutSystems applications.
  2. Healthcare Interoperability as a Service (coming soon) - for those who prefer a pay-per-use solution.

Contact KRE8 IT for more information about these options.


To see some examples of Patient data from the Interoperable Health Data Model and how these can be translated into the HL7 FHIR R4 Patient resources, or the other way around, you can try our Live Demo.


The following interoperable health data resources and their corresponding lists of options are included:

  • Account
  • Allergy Intolerance
  • Appointment
  • Appointment Response
  • Audit Event
  • Binary
  • Body Structure
  • Bundle
  • Care Team
  • Care Plan
  • Common (Shared)
  • Composition
  • Condition
  • Consent
  • Coverage
  • Diagnostic Report
  • Device
  • Document Reference
  • Encounter
  • Episode Of Care
  • Family Member History
  • Flag
  • Healthcare Service
  • Imaging Study
  • Immunization
  • List
  • Location
  • Medication
  • Medication Administration
  • Medication Dispense
  • Medication Request
  • Medication Statement
  • Observation
  • Operation Outcome
  • Organization
  • Patient
  • Person
  • Practitioner
  • Practitioner Role
  • Procedure
  • Provenance
  • Questionnaire
  • Questionnaire Response
  • Related Person
  • Schedule
  • Service Request
  • Slot
  • Specimen
  • Substance
  • Task

… with more coming soon.


This component does not use any AOs (Application Objects) at all.

Release notes (2.0.0)

New Documentation and Sample Application

We did our best to remove as much complexity as we could from the data model while keeping everything that’s required to make it interoperable. However, we realise that building Healthcare applications is inherently complex, and therefore we included a Sample Application and accompanying Documentation to explain the fundamentals to help you get started building an interoperable Digital Health application using this data model.


New Health Data Structures

We added 14 new interoperable health data structures in this release:

  • BodyStructure
  • CarePlan
  • Consent
  • Coverage
  • Device
  • Immunization
  • Medication
  • MedicationAdministration
  • MedicationDispense
  • MedicationRequest
  • MedicationStatement
  • Provenance
  • Specimen
  • Substance


New Versions of existing Data Structures

The following existing data structures now have new versions available and the previous versions have been deprecated:

  • AllergyIntolerance (v2)
  • AppointmentResponse (v2)
  • Binary (v2)
  • Bundle (v2)
  • Common_Attachment (v2)
  • Common_RelatedArtifact (v2)
  • Composition (v2)
  • DiagnosticReport (v2)
  • DocumentReference (v2)
  • Encounter (v2)
  • FamilyMemberHistory (v2)
  • HealthcareService (v2)
  • ImagingStudy (v2)
  • List (v2)
  • Location (v2)
  • Observation (v2)
  • OperationOutcome (v2)
  • Patient (v2)
  • Person (v2)
  • Practitioner (v2)
  • Procedure (v2)
  • Questionnaire (v2)
  • QuestionnaireResponse (v2)
  • RelatedPerson (v2)
  • Schedule (v2)
  • ServiceRequest (v2)
  • Slot (v2)
  • Task (v2)


NOTE: Each of the above data structures have corresponding Upgrade actions (e.g. Patient_Upgrade_v1_to_v2) that take in the v1 data structure and output the v2 data structure. These are private actions consumed by the new version’s Deserialize action, which will take the old version’s SimpleJSON and SimpleStructure (name) and it will automatically upgrade the data to return the data structure in the new version’s format. This streamlines the transition from an old data structure version to the new one.


New Attributes in existing Data Structures

The following new attributes have been added to some existing data structures:

  • Common_Reference_v1.Identifier
  • DiagnosticReport_Performer_v1.Reference
  • DiagnosticReport_Performer_v1.Type
  • DiagnosticReport_Performer_v1.Display
  • DiagnosticReport_Performer_v1.Identifier


New Serialize and Deserialize actions for each Data Structure

Each main Health Data Structure now has corresponding Serialize and Deserialize actions (e.g. Patient_Serialize_v2 and Patient_Deserialize_v2). The Serialize action takes in the Data Structure and returns the SimpleJSON and SimpleStructure name. These can be stored as a pair of attributes (e.g. in the ResourceVersion entity, as demonstrated in the companion Sample Application) and then passed to the Deserialize action when needed to return the full Data Structure.


Updates

Reference to OutSystems UI was updated to version 2.18.2.


Enhancements

Many of the data attribute descriptions have been updated with more complete information.


Fixes

Some data attributes had missing descriptions. These have been added.


DEPRECATED Service Actions replaced by Server Actions

Service Actions have been replaced with Server Actions for improved performance. The action names have the same name as the deprecated Service Actions, so all that is required to resolve this change in your consuming application is to Refresh References, remove the reference to the deprecated Service Action and select the new Server Action with the same name.

License (2.0.0)
Reviews (0)
Team
Other assets in this category