HL7 Norway FHIR DSTU-2 implementation guide

Package 'LabResult'

This section contains all the formal descriptions of how to apply HL7 FHIR to implement a LabResult client and service. These descriptions are collectively called 'conformance resources' in FHIR, and describe how Resources and the REST interface are adapted for use with the LabResult.

The following sections expect some familiarity with the conformance and profiling concepts of FHIR. If you want to learn more about these, you can read the background information in the FHIR specification. More information on how to develop software with FHIR in general and a FAQ can be found in the Help of this guide.

Client and Server interactions

Data about prescribers is exchanged between a LabResult Repository and a LabResult Client. The LabResult Repository exposes the information about the prescribers for interested clients using the FHIR REST interface. The LabResult Client can contact the LabResult Repository to query information about prescribers, either by searching on names or identifiers or by asking for any changes on the server since a point in time.

The client and server use the FHIR REST interface according to the current (May 2015) DSTU2 specification.

The formal responsibilities for both these actors are described in the following FHIR ConformanceStatements:

  • LabResult Repository, which are the formal requirements for a system acting as the LabResult Repository.
  • LabResult Client, which are the formal requirements for a system acting as a client to the the LabResult Repository.

Structures

In this usecase, the main Resources are the Observation and the DiagnosticReport Resources. The other Resources are added as contained Resources of these Resources. The performer of the lab research can either be an Organization Resource or a Practitioner Resource. The subject is always a Patient Resource and the specimen contains a Specimen Resource. The request field in the DiagnosticReport Resource contains the DiagnosticOrder Resource.

Which parts of these resources are relevant for the usecase and what additional constraints on their use are defined by this package, is described in the following FHIR StructureDefinitions:

Identifier systems

The data maintained by the LabResult has multiple data elements that represent Norwegian national identifiers for Practitioners and Organizations like HPRnumbers and RESH IDs. These identifiers are represented in FHIR by unique numbers within identifier systems, which themselves are registered names. Although these are not specific to this usecase and will ultimately be hosted on a national registry for such identifying systems, this implementation guide maintains a list of Norwegian identifier systems used for this usecase for the convenience of implementers.