Imaging Diagnostic Report, published by IHE Radiology Technical Committee. This is not an authorized publication; it is the continuous build for version 0.0.1-current. This version is based on the current content of https://github.com/IHE/RAD.IDR/ and changes regularly. See the Directory of published versions

1:XX IDR Home

Official URL: https://profiles.ihe.net/RAD/IDR/ImplementationGuide/ihe.rad.idr				Version: 0.0.1-current
Draft as of 2023-11-06				Computable Name: IHE_RAD_IDR

This Implementation Guide template includes skeleton pages for each part of an IHE supplement. The instructions for how to fill out these sections can be found in the included Supplement Template. This supplement template should not be included in your github repo or publication. It is included here for easy reference.

TODO: Write your executive overview here. Usually a one paragraph explanation of what problem this implementation guide solves.

Organization of This Guide

This guide is organized into the following sections:

1. Volume 1:
   1. Introduction
   2. Actors, Transactions, and Content
   3. Actor Options
   4. Actor Required Groupings
   5. Overview
   6. Security Considerations
   7. Cross Profile Considerations
   8. TODO: point to the Volume 1 Appendix if there is one
2. Volume 2: Transaction Detail
   1. ToDo do [domain-YY]
   2. TODO: point to the Volume 2 Appendix if there is one
3. Volume 3: Metadata and Content
   1. Content One
4. Volume 4: National Extensions
   1. TODO: point at the National Extensions if there are any
5. Other
   1. Test Plan
   2. Changes to Other IHE Specifications
   3. Download and Analysis

See also the Table of Contents and the index of Artifacts defined as part of this implementation guide.

Conformance Expectations

IHE uses the normative words: Shall, Should, and May according to standards conventions.

Must Support

The use of mustSupport in StructureDefinition profiles equivalent to the IHE use of R2 as defined in Appendix Z.

mustSupport of true - only has a meaning on items that are minimal cardinality of zero (0), and applies only to the source actor populating the data. The source actor shall populate the elements marked with MustSupport, if the concept is supported by the actor, a value exists, and security and consent rules permit. The consuming actors should handle these elements being populated or being absent/empty. Note that sometimes mustSupport will appear on elements with a minimal cardinality greater than zero (0), this is due to inheritance from a less constrained profile.