This page is part of the CH LAB-Order (R4) (v2.0.0-ballot: STU 2 Ballot 1) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
Home
Official URL: http://fhir.ch/ig/ch-lab-order/ImplementationGuide/ch.fhir.ig.ch-lab-order
This implementation guide is under STU ballot by HL7 Switzerland until September 30th, 2023 midnight.
Please add your feedback via the ‘Propose a change’-link in the footer on the page where you have comments.
HL7 Swiss FHIR Implementation Guide for generic laboratory order forms
This is HL7 Swiss FHIR implementation guide for Laboratory Orders, which is based on CH ORF (R4), Order & Referral by Form - Implementation Guide http://fhir.ch/ig/ch-orf/index.html, which refers on the CH Core Profiles of Switzerland and on CH EPR Term.
It also refers to FHIR Implementation Guide for Structured Data Capture (SDC) for creating user-friendly questionnaires SDC and targets forms that can be presented to the user with pre-filled input fields, and also provide guidance with searchable value sets.
There are some enhancements to the general Order and Referral implementation guide. Above all, samples play a major role in the laboratory and pathology area and must be closely linked to the order so that they can be correctly assigned in the executing laboratory. In general, the Laboratory Implementation Guide can also be used for pathology orders, which often follow the same path and are passed on from the laboratories to specialized pathology departments. And similar to other divisions, previous findings and images can also be requested. Many laboratories also offer services for monitoring vital signs, such as Blood pressure, ECG, pulse, which can be ordered.
This IG follows the Swiss eHealth Exchange Format Handbook Part I: Service Requests V 0.13. The Questionnaire resource gives gudiance for the implementaion of the user interface.
Download
You can download this Implementation Guide in NPM-format from here.
Foundation
Applications claiming for conformance with the CH LAB-Order Implementation Guide shall:
-Render (and in case of the Questionnaire filler allow for data entry) all elements of a questionnaire in the user interface (e.g. on screen, in print).
Customers of laboratories want to create their orders as efficiently and correctly as possible with the help of order forms. For this purpose, the laboratories provide forms that meet the following requirements:
The form should be able to be processed in their own informatics system (practice system, clinic system).
Pre-filled fields with information about the client, the patient, the commissioned laboratory, should facilitate the order process.
A Catalog (StructureDefinition Catalog) with the references of the examinations (Reference CatalogEntry) offered by the laboratory may be available. In order for the customer to be able to orientate himself in the abundance of possible examinations, it may be possible to search within laboratory specialties (Laboratory Order Panels). This part of the ordering process is here out of scope.
Sample properties (specimen), type of sample, vessel, etc., preanalytical specifications must be specified, and the customer must be able to provide additional information (e.g. oxygen flow rate, time of last meal, 24 h urine volume,). Parts of these informations can also be provided in a Catalog.
The order document should also cover other use cases. For example, a subsequent prescription of analyses on the same sample is foreseen, a common use case. It is also envisaged that the laboratory physician can make suggestions to the client for useful additional examinations, based on the original order.
Efficient commissioning places high demands on the standardisation and interoperability of data processing. The information systems of the client and the laboratory are involved. Likewise, the documents created should contain the required metadata for the EPD (Electronic Patient Dossier), and at the same time they can provide the metadata for the resulting diagnosis report.
Data exchange with different information systems (practice, hospital, laboratory) quickly becomes confusing due to proprietary solutions (n:m cardinality). Therefore, the question arises whether a standardised order system is not the more favourable solution in the long run.
The proposed solution consists of independent modules and can therefore be quickly adapted to new requirements. Thus, the laboratories can adapt their order panels and examinations in their catalogues as needed, as well as the structured data entry for additional information.
Five Case studies with examples for the Order Document
Using specific case histories, we have created five everyday examples of commissioned documents. These are requirements of examinations in the field of hematology, clinical chemistry, coagulation, infectious serology and microbiology. The last example covers the special case where several employees of a company send their biological material (serum, urine) to the laboratory for determination of substances hazardous to health (toxicology).
Copyright
This artefact includes content from SNOMED Clinical Terms® (SNOMED CT®) which is copyright of the International Health Terminology Standards Development Organisation (IHTSDO). Implementers of these artefacts must have the appropriate SNOMED CT Affiliate license - for more information contact http://www.snomed.org/snomed-ct/getsnomed-ct or info@snomed.org.
This document is licensed under Creative Commons “No Rights Reserved” (CC0).
HL7®, HEALTH LEVEL SEVEN®, FHIR® and the FHIR ® are trademarks owned by Health Level Seven International, registered with the United States Patent and Trademark Office.
This implementation guide contains and references intellectual property owned by third parties (“Third Party IP”). Acceptance of these License Terms does not grant any rights with respect to Third Party IP. The licensee alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize Third Party IP in connection with the specification or otherwise.
This publication includes IP covered under the following statements.
ISO Maintains the copyright on the country codes, and controls it's use carefully. For futher details see the ISO 3166 web page: https://www.iso.org/iso-3166-country-codes.html
The UCUM codes, UCUM table (regardless of format), and UCUM Specification are copyright 1999-2009, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved. https://ucum.org/trac/wiki/TermsOfUse
This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact http://www.snomed.org/snomed-ct/get-snomed-ct or info@snomed.org.
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 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.formatcode.fhir#1.1.0
Implementation Guide for IHE defined FormatCode vocabulary. (built Thu, Feb 24, 2022 16:55-0600-06:00)
Package ch.fhir.ig.ch-epr-term#2.0.9
Implementation guide for the meta data specified in the framework of Annex 3 and 9 of the FDHA Ordinance on the electronic patient record in Switzerland (built Tue, Jun 27, 2023 18:05+0200+02:00)
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 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 ch.fhir.ig.ch-epr-term#2.0.9
Implementation guide for the meta data specified in the framework of Annex 3 and 9 of the FDHA Ordinance on the electronic patient record in Switzerland (built Tue, Jun 27, 2023 18:05+0200+02:00)
Example resources in the R4 version of the FHIR standard
Package hl7.fhir.uv.sdc#3.0.0
The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR. This includes two components: * Support more sophisticated questionnaire/form use-cases such as those needed for research, oncology, pathology and other clinical domains. *Support pre-population and auto-population of EHR data into forms/questionnaires for uses outside direct clinical care (patient safety, adverse event reporting, public health reporting, etc.). (built Tue, Mar 8, 2022 18:32+0000+00:00)
Package ch.fhir.ig.ch-orf#2.0.0-ballot
Order & Referral by Form - Implementation Guide (CH ORF) (built Thu, Jun 29, 2023 21:19+0200+02:00)
An Order Catalog is an administered homogeneous collection of items such as medication products, laboratory tests, procedures, medical devices or knowledge artifacts such as order sets, which support the ordering process, or more generally healthcare processes. (built Sun, Aug 9, 2020 15:18+0000+00:00)
® are trademarks owned by Health Level Seven International, registered with the United States Patent and Trademark Office.
