HL7 FHIR Implementation Guide: Example IG Release 1 - US Realm | STU1
0.1.0 - STU1 International flag

HL7 FHIR Implementation Guide: Example IG Release 1 - US Realm | STU1, published by Jembi Health Systems. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/openhie/Training-Solution-1 and changes regularly. See the Directory of published versions

Home

Official URL: http://openhie.org/fhir/training-solution-1/ImplementationGuide/openhie.fhir.training.solution.1 Version: 0.1.0
Active as of 2022-03-24 Computable Name: TrainingSolution1

Contents:

This is a solution FHIR Implementation Guide (IG) to the hackathon concept note.

The purpose of the hackathon was to simulate a data exchange between an EMR and laboratory system through a planned practical demonstration. The overall intent of the planned practical was to allow participants to demonstrate what they have learnt through the creation of a FHIR IG where the use cases and data elements were provided by the lecturer.

Participants were required to deploy their FHIR IG to a lecturer provided centrally hosted platform per country and then demonstrate that their FHIR IG was able to support the use cases through a data exchange.

This FHIR IG not intended for production use but may be used to support the training needs of others.

For more information regarding the training course that was used to inform the aforementioned hackathon concept note, please see the FHIR training course guidelines.

Download

You can also download:

The source code for this Implementation Guide can be found on OpenHIE GitHub.

Cross Version Analysis

This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 (openhie.fhir.training.solution.1.r4) and R4B (openhie.fhir.training.solution.1.r4b) are available.

Dependency Table

Package hl7.fhir.uv.extensions.r4#1.0.0

This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00)

Package ihe.iti.pdqm#2.4.0

The Patient Demographics Query for Mobile (PDQm) Profile defines a lightweight RESTful interface to a patient demographics supplier leveraging technologies readily available to mobile applications and lightweight browser based applications. (built Tue, Feb 22, 2022 07:42-0600-06:00)

Package ihe.iti.balp#1.1.2

The Basic Audit Log Patterns (BALP) Implementation Guide is a Content Profile that defines some basic and reusable AuditEvent patterns. This includes basic audit log profiles for FHIR RESTful operations to be used when there is not a more specific audit event defined. A focus is enabling Privacy centric AuditEvent logs that hold well formed indication of the Patient when they are the subject of the activity being recorded in the log. Where a more specific audit event can be defined it should be derived off of these basic patterns. (built Tue, Aug 1, 2023 08:40-0500-05:00)

Package ihe.iti.pixm#3.0.3

ImplementationGuide for IHE IT Infrastructure Technical Framework Supplement Patient Identifier Cross-referencing for mobile (PIXm) (built Thu, Aug 3, 2023 15:56-0500-05:00)

Globals Table

There are no Global profiles defined

IP Statements

This publication includes IP covered under the following statements.

Intellectual Property Considerations

While this implementation guide and the underlying FHIR are licensed as public domain, this guide may include examples making use of terminologies such as LOINC, SNOMED CT and others which have more restrictive licensing requirements. Implementers should make themselves familiar with licensing and any other constraints of terminologies, questionnaires, and other components used as part of their implementation process. In some cases, licensing requirements may limit the systems that data captured using certain questionnaires may be shared with.

Disclaimer

This specification is provided without warranty of completeness or consistency, and the official publication supersedes this draft. No liability can be inferred from the use or misuse of this specification, or its consequences.