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 - 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
• Bundle
• Care Team
• Common (Shared)
• Composition
• Condition
• Diagnostic Report
• Document Reference
• Encounter
• Episode Of Care
• Family Member History
• Flag
• Healthcare Service
• Imaging Study
• List
• Location
• Observation
• Operation Outcome
• Organization
• Patient
• Person
• Practitioner
• Practitioner Role
• Procedure
• Questionnaire
• Questionnaire Response
• Related Person
• Schedule
• Service Request
• Slot
• Task

… with more coming soon.

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