CH RAD-Order (R4), published by HL7 Switzerland. This guide is not an authorized publication; it is the continuous build for version 2.0.0-ci-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7ch/ch-rad-order/ and changes regularly. See the Directory of published versions
Home
Official URL: http://fhir.ch/ig/ch-rad-order/ImplementationGuide/ch.fhir.ig.ch-rad-order
Download: You can download this implementation guide in npm format from here.
Foundation
This Implementation Guide uses FHIR defined resources. For details on HL7 FHIR R4 see http://hl7.org/fhir/r4.
Because the Implementation Guide relies heavily on the FHIR Resources Questionnaire and QuestionnaireResponse, forms are addressed here as Questionnaires.
There has been a discussion whether population of the resources such as Patient Resource, ServiceRequest Resource
etc. with the content of the QuestionnaireResponse Resource should be done by the order placer application or rather
by the order filler application. The argument for assigning the task to the order placer is a result of the following
consideration: the authors of a particular implementation guide may decide to define a questionnaire and its rendering but to leave it open if in a particular implementation the questionnaire is implemented or if the representation towards the user is made (in accordance to the questionnaire definition) by other technical means. In such a case, there would be no QuestionnaireResponse Resource in the bundle because all content is already in concerning resources. In order to handle all FHIR exchange formats equal (as far as sensible), the authors decided to mandate the order placer application with the task.
Applications claiming for conformance with the ORF 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). Grouping of items and the order of items within shall be adequately reproduced according to the questionnaire.
In case of an implementation without the resources Questionnaire and QuestionnaireResponse, the content of otherwise implemented user interfaces shall be in accordance to the questionnaire definition.
Be able to process all codes related to the generic elements in a Questionnaire.
Actors, transactions and safety considerations are covered in the corresponding sections of
CH ORF.
Systems such as PIS and KIS may not yet support RADIOLOGY PLAYBOOK. For this reason, CH RAD-Order allows coding of the relevant dimensions
by means of RADLEX.
The relevant dimensions are defined by PLAYBOOK such as:
Modality
Region
Focus
Laterality
Maneuvre
Guidance for action (used for interventions)
Coding of these dimensions is done by RADLEX terms.
IMPORTANT NOTICE: Value sets, in particular those containing Radlex terms, are still experimental. Definitive value sets will be defined when CH-Rad-Order becomes operational.All coding is preliminary and not yet approved by eHealth Suisse.
Previous Images
Results from earlier can be provided be means of attachments or - in case of DICOM SOP Instances - by means of a DICOM Service (e.g. WADO-RS). The ImagingStudy Resource allows for indicating DICOM tags such as SOP Instance UID, Series instance UID etc. DICOM Imaging data as well as other data (pdf, jpeg etc.) can be attached by means of a document reference.
The implementation of a DICOM service requires prerequisites in terms of infrastructure and policies (e.g. access rights). CH RAD-Order does not give guidance about that.
IMPORTANT NOTICE: Questionnaire items allowing entry for DICOM tags (such as study instance ID, series instance ID etc.) are for illustration / experimental use. A real world application shall hopefully provide other means for the selection of images / reports etc.
IP Statements
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.
Copyright 2014 – The Radiological Society of North America (RSNA), all rights reserved. Licensed under RadLex License Version 2.0. You may obtain a copy of the license at: http://www.rsna.org/radlexdownloads/This work is distributed under the above noted license on an “AS IS” basis, WITHOUT WARRANTIES OF ANY KIND, either express or implied. Please see the license for complete terms and conditions.Subject to the terms and conditions of this Agreement, Licensor hereby grants to You a worldwide, non-exclusive, no-charge, royalty-free copyright license to reproduce, prepare Adaptations of, publicly display, publicly perform, sublicense, and distribute the Work and such Adaptations in any medium.RadLex is licensed freely for commercial and non-commercial users. Review and download the license: http://www.rsna.org/uploadedFiles/RSNA/Content/Informatics/RadLex_License_Agreement_and_Terms_of_Use_V2_Final.pdf
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 https://www.snomed.org/get-snomed 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 Sat, Apr 27, 2024 18:39+1000+10:00)
Package ihe.formatcode.fhir#1.3.0
Implementation Guide for IHE defined FormatCode vocabulary. (built Fri, May 17, 2024 12:02-0500-05:00)
Package ch.fhir.ig.ch-term#current
Implementation Guide for Swiss Terminology (built Wed, Nov 27, 2024 10:08+0000+00: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)
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#3.0.0-ci-build
Order & Referral by Form - Implementation Guide (CH ORF) (built Fri, Nov 15, 2024 14:21+0000+00:00)
® are trademarks owned by Health Level Seven International, registered with the United States Patent and Trademark Office.
CH RAD-Order (R4)
