Laboratory Workflows Implementation Guide
0.3.0 - ci-build

Laboratory Workflows Implementation Guide - Local Development build (v0.3.0). See the Directory of published versions

Home

Computable Name:

This is the FHIR Implementation Guide for Laboratory Workflows between health information systems based on OpenHIE Specifications for Laboratory Workflows .

Summary

This Implementation Guide contains standards-compliant, open specifications for the transmission of Laboratory data between various health systems that are part of a Health Information Exchange (HIE). The contained specifications cover, for example, the following scenario:

  1. A Lab Test Order is made using an Electronic Medical Record (EMR) system
  2. The order is sent to a Lab Information System (LIS)
  3. The Lab Test is performed and resulted
  4. The results are sent back to the EMR for review by the medical team and patients

This IG is based on guidance from the FHIR documentation on the Workflow Module and specifically the suggested Communication Patterns.

About this IG

The top menu allows quick navigation to the different sections, and a Table of Contents is provided with the entire content of this Implementation Guide. (Be aware that some pages have multiple tabs).

Intellectual Property Considerations

While this implementation guide and the underlying FHIR are licensed as public domain, this guide includes 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

The specification herewith documented is a demo working specification, and may not be used for any implementation purposes. This draft 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.