HL7 Czech Imaging Order IG
0.1.0-ballot - ballot Czechia flag

HL7 Czech Imaging Order IG, published by HL7 Czech Republic. This guide is not an authorized publication; it is the continuous build for version 0.1.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7-cz/img-order/ and changes regularly. See the Directory of published versions

Resource Profile: Composition: Imaging Order (CZ)

Official URL: https://hl7.cz/fhir/img-order/StructureDefinition/cz-compositionImageOrder Version: 0.1.0-ballot
Standards status: Draft Maturity Level: 0 Computable Name: CZ_CompositionImageOrder

Copyright/Legal: HL7 CZ

Clinical document used to represent a Imaging Order for the scope of this guide.

Imaging order bundle is an electronic health record extract containing order for imaging observation from a subject of care, comprising at least the required elements of the imaging dataset.

Imaging Order structure

Imaging Order Header

Patient Identification

This section contains records about the patient such as his identifiers, name or address.

Patient Contact Information

The section contains contact information for people who can provide additional information about the patient. There may also be a contact for another doctor. This information is especially necessary for patients with rare diseases.

The type of contact person distinguishes between emergency contacts, legal representatives and other persons related to patients. This is a definition of contact persons who can be contacted to prepare the patient for the examination or in other cases.

Health Insurance

The patient's health insurance, which may not necessarily be the payer for completing the given request form.

Coverage

Contains information on how the examination will be paid.

Author

Contains identification of the healthcare professional or other person ordering the examination.

Requested Performer

Contains information about the person who will process the request form (the processor will not be specified for unaddressed requests).

Additional Recipient

May contain the identification of additional recipients of the finding in addition to the ordering party.

Document Metadata

Contains additional information about the request document such as: Document administrator.

Digital Signatures

The content of this section is the electronic signature of the document according to Act 327/2011 §54a.

Body of the Imaging Order

Order Information

This mandatory section includes the required order identifier (A.2.1.1) and the date and time of its creation (A.2.1.2) — if the information section is established, it must contain these details. Optional items include the urgency of the order (from the perspective of Indicating Physician) expressed by an international code from the HL7 system (Request Priority) (A.2.1.4), which can have values such as routine (normal priority), urgent (urgent case), asap (as soon as possible) and stat (status iminens / STATIM). Another optional item is the requested date and time of the examination (A.2.1.3), which does not refer to the actual booking date but opens the possibility, for example, to send an order form with a request for scheduling on the day when the patient has an outpatient clinical check-up.

Additional Requirements / Detailed Examination Specifications (A.2.1.5) is another optional field that can contain extra information for the order. This could include, for example, the Referring physician request for using a specific agreed-upon protocol or conducting the examination on a specific MRI machine.

The final optional item is information for the patient, such as fasting requirements, medication discontinuation, advice on claustrophobia, etc.

Justification for Examination (Reason for Order)

This required section includes the indicative diagnosis (A.2.2.1), which is required by health insurance companies for service reimbursement. Additional items include the clinical question (an interrogative sentence that should end with a question mark and should be answerable based on the imaging examination) which can also be assigned a SNOMED CT code, and the reason for the order (essentially a brief summary, again with the option to encode the information). The advantage of using a code in the future could be the integration with existing information in the Indicating Physician's system within the NIS (Nursing Information System), thereby eliminating the need to re-enter this information.

Examination Appointment (Visit)

This mandatory section includes confirmed information from the examining healthcare facility about the appointment, such as when the patient is scheduled, where they need to go, and may include free text comments (e.g. MRI on the 2nd floor of the main building). The use of these structures assumes that it will be possible, after the order has been received by the examining healthcare facility, to "supplement" this information or create an updated version of the order form that includes this information.

Clinical Information (Anamnesis)

This required section includes biometric data (weight and height), other clinically relevant information in free text or optionally with an MKN-10 code (e.g. claustrophobia in an MRI order) or Orphacode, medication information (relevant, for example, before a contrast examination on CT), implant information (for MRI) and urgent information (allergies, intolerances or any other warnings in free text). The urgent information module is a component common to other models. Additional formalized data can help convey any information about the patient (e.g. week of gestation before a gynecological ultrasound examination). Additionally, clinical information should include any patient limitations (e.g. wheelchair-bound, bedridden, blind, hearing impaired).

Order/Examination Data Elements

This required section includes the data elements of the requested examination and it consists of the six most important items (the entire block can appear multiple times, e.g. for MRI of the brain and cervical spine):

1) Examination Code – SNOMED CT code representing the examination.

2) Examination Name – Optional text independent of coded data.

3) Modality – Based on the international DICOM modalities registry and/or its SNOMED CT equivalent. A limitation is that, for example, an X-ray can be performed in three ways (DICOM modalities):

  • RTG – Conventional film image, which is then scanned
  • Computed radiography (CR) from a machine with indirect digitalization
  • DX from a machine with direct digitalization

    Given the decline of RTG and CR, it can be assumed for order purposes that the requested examination is DX. If the examination is performed with a different X-ray modality, it should not be an issue, as secondary modalities would also be mapped to X-ray/plain films. The mapping of DICOM attributes is handled by the dicom_modality table.

4) Body Part – A part of the SNOMED CT registry defined by the DICOM standard. The reason is that the complete set of SNOMED CT values contains general body parts (e.g. tendon), which are not useful for imaging examinations. We need to know whether the tendon is on the hand or the foot.

5) Laterality – In this case, the use of SNOMED CT values is preferred. When it is not possible to indicate examination of both sides, separate values should be created for the left and right sides.

6) Note – Space for a text note related to the examination.

Examination Appointment (Visit)

This required section includes confirmed information from the examining Healthcare Facility about the appointment, such as when the patient is scheduled, where they should go, and may include free text comments (e.g. MRI on the 2nd floor of the main building). The use of these structures assumes that, after the examination request is received by the Healthcare Facility, it will be possible to "supplement" or update the order to include this information, thereby creating an updated version of the order form.

Attachments

This optional section allows for the inclusion of any additional sources of information, such as outpatient reports, discharge summaries (in digital form or even just a scan), data provided by the patient, etc. While this section is not mandatory, it provides the flexibility to attach various types of files or documents to supplement the order form with relevant information.

Sample Information (Specimen)

This required section is consistent with laboratory procedures. The term "container" refers to any kind of "packaging" for the sample and does not indicate a specific device. In radiology, it sometimes occurs that we image a biopsy sample (e.g. obtained from a breast biopsy or intraoperatively). Although most facilities do not formally create an order for this type of image, it is process-wise appropriate to account for this possibility. Therefore, we propose including this section in the standard, even though we anticipate it may not be widely used initially.

Payment

This section allows for specification if part of the examination is covered differently than the majority of it (e.g. special reconstructions not covered by insurance). While this section is required to be present, it is not mandatory to fill it out, meaning it can be left blank if not applicable.

A free text comment on payment can be used when there is a need to specify which part of the care is covered by a different payer. This allows for clarity and transparency regarding the financial responsibilities and arrangements associated with the provided healthcare services.

Clinical Encounter (Encounter)

This optional section allows for linking the order form to a specific clinical encounter, such as an outpatient visit during which the order was created. Although this information is not crucial for the examination itself, it provides a way to connect the order with outpatient or other reports that may contain relevant information not included on the order form by the clinician. This linkage can enhance the context and understanding of the patient's clinical situation and ensure all pertinent details are considered in the diagnostic or treatment process.

Planned care orders

This section contains references to scheduled care plan orders that follow from this order form. Besides the ID, it should include the name of the appointment, with other details being automatically populated from the referenced order. For example, an entry may state "Consultation in Neurosurgery" and by using the ID, one can determine that it is scheduled at the Central Military Hospital on March 15, 2040, at 16:15. This facilitates efficient tracking and management of the patient’s care pathway.

Other Supporting Information

This section is intended for additional supportive information, such as specifying when the results will be needed (for subsequent care, surgery, etc.). It is included to enable linking not only to follow-up appointments or outpatient examinations (as facilitated by the appointment section above) but also to other significant events, such as a scheduled surgery date. Similar to the previous example, necessary details should be retrieved based on an ID, allowing the user to see, for instance, "Gallbladder surgery on March 16, 2040, at VFN Prague". This helps ensure relevant scheduling and planning information is readily accessible to healthcare providers.

Usages:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Composition C 0..* Composition Imaging Order Composition
Constraints: text-or-section
... meta Σ 0..1 Meta Metadata about the resource
.... security SΣ 0..* Coding Security Labels applied to this resource
Binding: All Security Labels (extensible): Security Labels from the Healthcare Privacy and Security Classification System.
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
... status ?!Σ 1..1 code Status of the Order
Binding: CompositionStatus (required): The workflow/clinical status of the composition.
... type Σ 1..1 CodeableConcept Kind of composition (LOINC if possible)
Binding: Valueset of types Clinical event (CZ) (required)
... category Σ 0..* CodeableConcept Categorization of Composition
Binding: DocumentClassValueSet (required)
... subject Σ 1..1 Reference(Patient (CZ core)) Who and/or what the composition is about
... encounter Σ 0..1 Reference(Encounter: Imaging Order (CZ)) Context that defines the Imaging Order
... date Σ 1..1 dateTime Date the order was created.
... author Σ 1..* Reference(Practitioner (CZ core) | Device: Performer/Observer (CZ)) Who and/or what authored the Imaging order
... title Σ 1..1 string Human Readable name/title
... custodian Σ 0..1 Reference(Organization (CZ core)) Organization that manages the Imaging Order
... Slices for section C 2..* BackboneElement Sections composing the Imaging Order
Slice: Unordered, Open by value:code
Constraints: cmp-1, cmp-2
.... section:All Slices Content/Rules for all slices
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... section:orderInformation C 1..* BackboneElement Order Information
Constraints: cmp-1, cmp-2
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 55115-0
....... display 1..1 string Representation defined by the system
Fixed Value: Requested imaging studies information Document
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... entry C 0..* Reference(Service Request: Imaging Order (CZ)) A reference to data that supports this section
.... section:clinicalQuestion C 1..* BackboneElement Clinical question
Constraints: cmp-1, cmp-2
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 18785-6
....... display 1..1 string Representation defined by the system
Fixed Value: Radiology Reason for study (narrative)
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... author 0..* Reference(Practitioner (CZ core) | Practitioner Role (CZ core) | Device: Performer/Observer (CZ) | Patient (CZ core) | Related Person (CZ core) | Organization (CZ core)) Who and/or what authored the section
..... text C 1..1 Narrative Text summary of the section, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... entry C 0..* Reference(Condition: Imaging Order (CZ)) A reference to data that supports this section
.... section:coverage C 0..* BackboneElement Coverage type
Constraints: cmp-1, cmp-2
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 87520-3
....... display 1..1 string Representation defined by the system
Fixed Value: Coverage type
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... entry C 0..* Reference(Coverage (CZ)) A reference to data that supports this section
.... section:appointment C 0..1 BackboneElement Appointment
Constraints: cmp-1, cmp-2
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 56446-8
....... display 1..1 string Representation defined by the system
Fixed Value: Appointment summary Document
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... entry C 0..* Reference(Appointment: Imaging Order (CZ)) A reference to data that supports this section
.... section:carePlan C 0..1 BackboneElement Care Plan
Constraints: cmp-1, cmp-2
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 18776-5
....... display 1..1 string Representation defined by the system
Fixed Value: Plan of care note
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... entry C 0..* Reference(Care plan: Imaging Order (CZ)) A reference to data that supports this section
.... section:medicalDevices C 0..* BackboneElement Medical Devices and implants
Constraints: cmp-1, cmp-2
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 97813-0
....... display 1..1 string Representation defined by the system
Fixed Value: Implant component
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... entry C 0..* Reference(Device Use Statement: Imaging Order (CZ)) A reference to data that supports this section
.... section:attachments C 0..* BackboneElement Library of attachments
Constraints: cmp-1, cmp-2
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 77599-9
....... display 1..1 string Representation defined by the system
Fixed Value: Additional documentation
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... entry C 0..* Reference(Attachment: Imaging Order (CZ)) A reference to data that supports this section

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / CodeURI
Composition.meta.securityextensibleAll Security Labels
http://hl7.org/fhir/ValueSet/security-labels
From the FHIR Standard
Composition.statusrequiredCompositionStatus
http://hl7.org/fhir/ValueSet/composition-status|4.0.1
From the FHIR Standard
Composition.typerequiredCZ_TypeClinicalEventVs(a valid code from Codesystem of Clinical Event Type)
https://hl7.cz/fhir/img-order/ValueSet/cz-typeClinicalEvent-vs
From this IG
Composition.categoryrequiredDocumentClassValueSet
http://hl7.org/fhir/ValueSet/document-classcodes
From the FHIR Standard
Composition.section:orderInformation.codeexamplePattern Value: LOINC Code 55115-0("Requested imaging studies information Document")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:clinicalQuestion.codeexamplePattern Value: LOINC Code 18785-6("Radiology Reason for study (narrative)")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:coverage.codeexamplePattern Value: LOINC Code 87520-3("Coverage type")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:appointment.codeexamplePattern Value: LOINC Code 56446-8("Appointment summary Document")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:carePlan.codeexamplePattern Value: LOINC Code 18776-5("Plan of care note")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:medicalDevices.codeexamplePattern Value: LOINC Code 97813-0("Implant component")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:attachments.codeexamplePattern Value: LOINC Code 77599-9("Additional documentation")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard

Constraints

IdGradePath(s)DetailsRequirements
cmp-1errorComposition.section, Composition.section:orderInformation, Composition.section:clinicalQuestion, Composition.section:coverage, Composition.section:appointment, Composition.section:carePlan, Composition.section:medicalDevices, Composition.section:attachmentsA section must contain at least one of text, entries, or sub-sections
: text.exists() or entry.exists() or section.exists()
cmp-2errorComposition.section, Composition.section:orderInformation, Composition.section:clinicalQuestion, Composition.section:coverage, Composition.section:appointment, Composition.section:carePlan, Composition.section:medicalDevices, Composition.section:attachmentsA section can only have an emptyReason if it is empty
: emptyReason.empty() or entry.empty()
dom-2errorCompositionIf the resource is contained in another resource, it SHALL NOT contain nested Resources
: contained.contained.empty()
dom-3errorCompositionIf the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
: contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4errorCompositionIf a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
: contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5errorCompositionIf a resource is contained in another resource, it SHALL NOT have a security label
: contained.meta.security.empty()
dom-6best practiceCompositionA resource should have narrative for robust management
: text.`div`.exists()
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()
text-or-sectionerrorCompositionA Composition SHALL have either text, at least one section, or both.
: text.exists() or section.exists()

This structure is derived from Composition

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Composition C 0..* Composition Imaging Order Composition
Constraints: text-or-section
... meta
.... security S 0..* Coding Security Labels applied to this resource
... identifier 0..1 Identifier Order identifier
... status 1..1 code Status of the Order
... category 0..* CodeableConcept Categorization of Composition
Binding: DocumentClassValueSet (required)
... subject 1..1 Reference(Patient (CZ core)) Who and/or what the composition is about
... encounter 0..1 Reference(Encounter: Imaging Order (CZ)) Context that defines the Imaging Order
... date 1..1 dateTime Date the order was created.
... author 1..* Reference(Practitioner (CZ core) | Device: Performer/Observer (CZ)) Who and/or what authored the Imaging order
... custodian 0..1 Reference(Organization (CZ core)) Organization that manages the Imaging Order
... Slices for section 2..* BackboneElement Sections composing the Imaging Order
Slice: Unordered, Open by value:code
.... section:orderInformation 1..* BackboneElement Order Information
..... code 1..1 CodeableConcept Classification of section (recommended)
Required Pattern: At least the following
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 55115-0
....... display 1..1 string Representation defined by the system
Fixed Value: Requested imaging studies information Document
..... entry 0..* Reference(Service Request: Imaging Order (CZ)) A reference to data that supports this section
.... section:clinicalQuestion 1..* BackboneElement Clinical question
..... code 1..1 CodeableConcept Classification of section (recommended)
Required Pattern: At least the following
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 18785-6
....... display 1..1 string Representation defined by the system
Fixed Value: Radiology Reason for study (narrative)
..... author 0..* Reference(Practitioner (CZ core) | Practitioner Role (CZ core) | Device: Performer/Observer (CZ) | Patient (CZ core) | Related Person (CZ core) | Organization (CZ core)) Who and/or what authored the section
..... text 1..1 Narrative Text summary of the section, for human interpretation
..... entry 0..* Reference(Condition: Imaging Order (CZ)) A reference to data that supports this section
.... section:coverage 0..* BackboneElement Coverage type
..... code 1..1 CodeableConcept Classification of section (recommended)
Required Pattern: At least the following
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 87520-3
....... display 1..1 string Representation defined by the system
Fixed Value: Coverage type
..... entry 0..* Reference(Coverage (CZ)) A reference to data that supports this section
.... section:appointment 0..1 BackboneElement Appointment
..... code 1..1 CodeableConcept Classification of section (recommended)
Required Pattern: At least the following
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 56446-8
....... display 1..1 string Representation defined by the system
Fixed Value: Appointment summary Document
..... entry 0..* Reference(Appointment: Imaging Order (CZ)) A reference to data that supports this section
.... section:carePlan 0..1 BackboneElement Care Plan
..... code 1..1 CodeableConcept Classification of section (recommended)
Required Pattern: At least the following
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 18776-5
....... display 1..1 string Representation defined by the system
Fixed Value: Plan of care note
..... entry 0..* Reference(Care plan: Imaging Order (CZ)) A reference to data that supports this section
.... section:medicalDevices 0..* BackboneElement Medical Devices and implants
..... code 1..1 CodeableConcept Classification of section (recommended)
Required Pattern: At least the following
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 97813-0
....... display 1..1 string Representation defined by the system
Fixed Value: Implant component
..... entry 0..* Reference(Device Use Statement: Imaging Order (CZ)) A reference to data that supports this section
.... section:attachments 0..* BackboneElement Library of attachments
..... code 1..1 CodeableConcept Classification of section (recommended)
Required Pattern: At least the following
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 77599-9
....... display 1..1 string Representation defined by the system
Fixed Value: Additional documentation
..... entry 0..* Reference(Attachment: Imaging Order (CZ)) A reference to data that supports this section

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
Composition.typerequiredCZ_TypeClinicalEventVs(a valid code from Codesystem of Clinical Event Type)
https://hl7.cz/fhir/img-order/ValueSet/cz-typeClinicalEvent-vs
From this IG
Composition.categoryrequiredDocumentClassValueSet
http://hl7.org/fhir/ValueSet/document-classcodes
From the FHIR Standard

Constraints

IdGradePath(s)DetailsRequirements
text-or-sectionerrorCompositionA Composition SHALL have either text, at least one section, or both.
: text.exists() or section.exists()
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Composition C 0..* Composition Imaging Order Composition
Constraints: text-or-section
... id Σ 0..1 id Logical id of this artifact
... meta Σ 0..1 Meta Metadata about the resource
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
.... versionId Σ 0..1 id Version specific identifier
.... lastUpdated Σ 0..1 instant When the resource version last changed
.... source Σ 0..1 uri Identifies where the resource comes from
.... profile Σ 0..* canonical(StructureDefinition) Profiles this resource claims to conform to
.... security SΣ 0..* Coding Security Labels applied to this resource
Binding: All Security Labels (extensible): Security Labels from the Healthcare Privacy and Security Classification System.
.... tag Σ 0..* Coding Tags applied to this resource
Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... text 0..1 Narrative Text summary of the resource, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
... contained 0..* Resource Contained, inline Resources
... extension 0..* Extension Additional content defined by implementations
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
... identifier Σ 0..1 Identifier Order identifier
... status ?!Σ 1..1 code Status of the Order
Binding: CompositionStatus (required): The workflow/clinical status of the composition.
... type Σ 1..1 CodeableConcept Kind of composition (LOINC if possible)
Binding: Valueset of types Clinical event (CZ) (required)
... category Σ 0..* CodeableConcept Categorization of Composition
Binding: DocumentClassValueSet (required)
... subject Σ 1..1 Reference(Patient (CZ core)) Who and/or what the composition is about
... encounter Σ 0..1 Reference(Encounter: Imaging Order (CZ)) Context that defines the Imaging Order
... date Σ 1..1 dateTime Date the order was created.
... author Σ 1..* Reference(Practitioner (CZ core) | Device: Performer/Observer (CZ)) Who and/or what authored the Imaging order
... title Σ 1..1 string Human Readable name/title
... confidentiality Σ 0..1 code As defined by affinity domain
Binding: v3.ConfidentialityClassification (2014-03-26) (required): Codes specifying the level of confidentiality of the composition.
... attester 0..* BackboneElement Attests to accuracy of composition
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... mode 1..1 code personal | professional | legal | official
Binding: CompositionAttestationMode (required): The way in which a person authenticated a composition.
.... time 0..1 dateTime When the composition was attested
.... party 0..1 Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization) Who attested the composition
... custodian Σ 0..1 Reference(Organization (CZ core)) Organization that manages the Imaging Order
... relatesTo 0..* BackboneElement Relationships to other compositions/documents
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... code 1..1 code replaces | transforms | signs | appends
Binding: DocumentRelationshipType (required): The type of relationship between documents.
.... target[x] 1..1 Target of the relationship
..... targetIdentifier Identifier
..... targetReference Reference(Composition)
... event Σ 0..* BackboneElement The clinical service(s) being documented
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... code Σ 0..* CodeableConcept Code(s) that apply to the event being documented
Binding: ActCode (3.0.0) (example): This list of codes represents the main clinical acts being documented.
.... period Σ 0..1 Period The period covered by the documentation
.... detail Σ 0..* Reference(Resource) The event(s) being documented
... Slices for section C 2..* BackboneElement Sections composing the Imaging Order
Slice: Unordered, Open by value:code
Constraints: cmp-1, cmp-2
.... section:All Slices Content/Rules for all slices
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... title 0..1 string Label for section (e.g. for ToC)
..... code 0..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
..... author 0..* Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization) Who and/or what authored the section
..... focus 0..1 Reference(Resource) Who/what the section is about, when it is not about the subject of composition
..... text C 0..1 Narrative Text summary of the section, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... mode 0..1 code working | snapshot | changes
Binding: ListMode (required): The processing mode that applies to this section.
..... orderedBy 0..1 CodeableConcept Order of section entries
Binding: ListOrderCodes (preferred): What order applies to the items in the entry.
..... entry C 0..* Reference(Resource) A reference to data that supports this section
..... emptyReason C 0..1 CodeableConcept Why the section is empty
Binding: ListEmptyReasons (preferred): If a section is empty, why it is empty.
..... section C 0..* See section (Composition) Nested Section
.... section:orderInformation C 1..* BackboneElement Order Information
Constraints: cmp-1, cmp-2
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... title 0..1 string Label for section (e.g. for ToC)
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 55115-0
....... display 1..1 string Representation defined by the system
Fixed Value: Requested imaging studies information Document
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... author 0..* Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization) Who and/or what authored the section
..... focus 0..1 Reference(Resource) Who/what the section is about, when it is not about the subject of composition
..... text C 0..1 Narrative Text summary of the section, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... mode 0..1 code working | snapshot | changes
Binding: ListMode (required): The processing mode that applies to this section.
..... orderedBy 0..1 CodeableConcept Order of section entries
Binding: ListOrderCodes (preferred): What order applies to the items in the entry.
..... entry C 0..* Reference(Service Request: Imaging Order (CZ)) A reference to data that supports this section
..... emptyReason C 0..1 CodeableConcept Why the section is empty
Binding: ListEmptyReasons (preferred): If a section is empty, why it is empty.
..... section C 0..* See section (Composition) Nested Section
.... section:clinicalQuestion C 1..* BackboneElement Clinical question
Constraints: cmp-1, cmp-2
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... title 0..1 string Label for section (e.g. for ToC)
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 18785-6
....... display 1..1 string Representation defined by the system
Fixed Value: Radiology Reason for study (narrative)
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... author 0..* Reference(Practitioner (CZ core) | Practitioner Role (CZ core) | Device: Performer/Observer (CZ) | Patient (CZ core) | Related Person (CZ core) | Organization (CZ core)) Who and/or what authored the section
..... focus 0..1 Reference(Resource) Who/what the section is about, when it is not about the subject of composition
..... text C 1..1 Narrative Text summary of the section, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... mode 0..1 code working | snapshot | changes
Binding: ListMode (required): The processing mode that applies to this section.
..... orderedBy 0..1 CodeableConcept Order of section entries
Binding: ListOrderCodes (preferred): What order applies to the items in the entry.
..... entry C 0..* Reference(Condition: Imaging Order (CZ)) A reference to data that supports this section
..... emptyReason C 0..1 CodeableConcept Why the section is empty
Binding: ListEmptyReasons (preferred): If a section is empty, why it is empty.
..... section C 0..* See section (Composition) Nested Section
.... section:coverage C 0..* BackboneElement Coverage type
Constraints: cmp-1, cmp-2
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... title 0..1 string Label for section (e.g. for ToC)
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 87520-3
....... display 1..1 string Representation defined by the system
Fixed Value: Coverage type
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... author 0..* Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization) Who and/or what authored the section
..... focus 0..1 Reference(Resource) Who/what the section is about, when it is not about the subject of composition
..... text C 0..1 Narrative Text summary of the section, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... mode 0..1 code working | snapshot | changes
Binding: ListMode (required): The processing mode that applies to this section.
..... orderedBy 0..1 CodeableConcept Order of section entries
Binding: ListOrderCodes (preferred): What order applies to the items in the entry.
..... entry C 0..* Reference(Coverage (CZ)) A reference to data that supports this section
..... emptyReason C 0..1 CodeableConcept Why the section is empty
Binding: ListEmptyReasons (preferred): If a section is empty, why it is empty.
..... section C 0..* See section (Composition) Nested Section
.... section:appointment C 0..1 BackboneElement Appointment
Constraints: cmp-1, cmp-2
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... title 0..1 string Label for section (e.g. for ToC)
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 56446-8
....... display 1..1 string Representation defined by the system
Fixed Value: Appointment summary Document
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... author 0..* Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization) Who and/or what authored the section
..... focus 0..1 Reference(Resource) Who/what the section is about, when it is not about the subject of composition
..... text C 0..1 Narrative Text summary of the section, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... mode 0..1 code working | snapshot | changes
Binding: ListMode (required): The processing mode that applies to this section.
..... orderedBy 0..1 CodeableConcept Order of section entries
Binding: ListOrderCodes (preferred): What order applies to the items in the entry.
..... entry C 0..* Reference(Appointment: Imaging Order (CZ)) A reference to data that supports this section
..... emptyReason C 0..1 CodeableConcept Why the section is empty
Binding: ListEmptyReasons (preferred): If a section is empty, why it is empty.
..... section C 0..* See section (Composition) Nested Section
.... section:carePlan C 0..1 BackboneElement Care Plan
Constraints: cmp-1, cmp-2
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... title 0..1 string Label for section (e.g. for ToC)
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 18776-5
....... display 1..1 string Representation defined by the system
Fixed Value: Plan of care note
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... author 0..* Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization) Who and/or what authored the section
..... focus 0..1 Reference(Resource) Who/what the section is about, when it is not about the subject of composition
..... text C 0..1 Narrative Text summary of the section, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... mode 0..1 code working | snapshot | changes
Binding: ListMode (required): The processing mode that applies to this section.
..... orderedBy 0..1 CodeableConcept Order of section entries
Binding: ListOrderCodes (preferred): What order applies to the items in the entry.
..... entry C 0..* Reference(Care plan: Imaging Order (CZ)) A reference to data that supports this section
..... emptyReason C 0..1 CodeableConcept Why the section is empty
Binding: ListEmptyReasons (preferred): If a section is empty, why it is empty.
..... section C 0..* See section (Composition) Nested Section
.... section:medicalDevices C 0..* BackboneElement Medical Devices and implants
Constraints: cmp-1, cmp-2
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... title 0..1 string Label for section (e.g. for ToC)
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 97813-0
....... display 1..1 string Representation defined by the system
Fixed Value: Implant component
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... author 0..* Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization) Who and/or what authored the section
..... focus 0..1 Reference(Resource) Who/what the section is about, when it is not about the subject of composition
..... text C 0..1 Narrative Text summary of the section, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... mode 0..1 code working | snapshot | changes
Binding: ListMode (required): The processing mode that applies to this section.
..... orderedBy 0..1 CodeableConcept Order of section entries
Binding: ListOrderCodes (preferred): What order applies to the items in the entry.
..... entry C 0..* Reference(Device Use Statement: Imaging Order (CZ)) A reference to data that supports this section
..... emptyReason C 0..1 CodeableConcept Why the section is empty
Binding: ListEmptyReasons (preferred): If a section is empty, why it is empty.
..... section C 0..* See section (Composition) Nested Section
.... section:attachments C 0..* BackboneElement Library of attachments
Constraints: cmp-1, cmp-2
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... title 0..1 string Label for section (e.g. for ToC)
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 77599-9
....... display 1..1 string Representation defined by the system
Fixed Value: Additional documentation
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... author 0..* Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization) Who and/or what authored the section
..... focus 0..1 Reference(Resource) Who/what the section is about, when it is not about the subject of composition
..... text C 0..1 Narrative Text summary of the section, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... mode 0..1 code working | snapshot | changes
Binding: ListMode (required): The processing mode that applies to this section.
..... orderedBy 0..1 CodeableConcept Order of section entries
Binding: ListOrderCodes (preferred): What order applies to the items in the entry.
..... entry C 0..* Reference(Attachment: Imaging Order (CZ)) A reference to data that supports this section
..... emptyReason C 0..1 CodeableConcept Why the section is empty
Binding: ListEmptyReasons (preferred): If a section is empty, why it is empty.
..... section C 0..* See section (Composition) Nested Section

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / CodeURI
Composition.meta.securityextensibleAll Security Labels
http://hl7.org/fhir/ValueSet/security-labels
From the FHIR Standard
Composition.meta.tagexampleCommonTags
http://hl7.org/fhir/ValueSet/common-tags
From the FHIR Standard
Composition.languagepreferredCommonLanguages
http://hl7.org/fhir/ValueSet/languages
From the FHIR Standard
Additional Bindings Purpose
AllLanguages Max Binding
Composition.statusrequiredCompositionStatus
http://hl7.org/fhir/ValueSet/composition-status|4.0.1
From the FHIR Standard
Composition.typerequiredCZ_TypeClinicalEventVs(a valid code from Codesystem of Clinical Event Type)
https://hl7.cz/fhir/img-order/ValueSet/cz-typeClinicalEvent-vs
From this IG
Composition.categoryrequiredDocumentClassValueSet
http://hl7.org/fhir/ValueSet/document-classcodes
From the FHIR Standard
Composition.confidentialityrequiredv3.ConfidentialityClassification
http://terminology.hl7.org/ValueSet/v3-ConfidentialityClassification|2014-03-26
From the FHIR Standard
Composition.attester.moderequiredCompositionAttestationMode
http://hl7.org/fhir/ValueSet/composition-attestation-mode|4.0.1
From the FHIR Standard
Composition.relatesTo.coderequiredDocumentRelationshipType
http://hl7.org/fhir/ValueSet/document-relationship-type|4.0.1
From the FHIR Standard
Composition.event.codeexampleActCode
http://terminology.hl7.org/ValueSet/v3-ActCode|3.0.0
Composition.section.codeexampleDocumentSectionCodes
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section.moderequiredListMode
http://hl7.org/fhir/ValueSet/list-mode|4.0.1
From the FHIR Standard
Composition.section.orderedBypreferredListOrderCodes
http://hl7.org/fhir/ValueSet/list-order
From the FHIR Standard
Composition.section.emptyReasonpreferredListEmptyReasons
http://hl7.org/fhir/ValueSet/list-empty-reason
From the FHIR Standard
Composition.section:orderInformation.codeexamplePattern Value: LOINC Code 55115-0("Requested imaging studies information Document")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:orderInformation.moderequiredListMode
http://hl7.org/fhir/ValueSet/list-mode|4.0.1
From the FHIR Standard
Composition.section:orderInformation.orderedBypreferredListOrderCodes
http://hl7.org/fhir/ValueSet/list-order
From the FHIR Standard
Composition.section:orderInformation.emptyReasonpreferredListEmptyReasons
http://hl7.org/fhir/ValueSet/list-empty-reason
From the FHIR Standard
Composition.section:clinicalQuestion.codeexamplePattern Value: LOINC Code 18785-6("Radiology Reason for study (narrative)")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:clinicalQuestion.moderequiredListMode
http://hl7.org/fhir/ValueSet/list-mode|4.0.1
From the FHIR Standard
Composition.section:clinicalQuestion.orderedBypreferredListOrderCodes
http://hl7.org/fhir/ValueSet/list-order
From the FHIR Standard
Composition.section:clinicalQuestion.emptyReasonpreferredListEmptyReasons
http://hl7.org/fhir/ValueSet/list-empty-reason
From the FHIR Standard
Composition.section:coverage.codeexamplePattern Value: LOINC Code 87520-3("Coverage type")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:coverage.moderequiredListMode
http://hl7.org/fhir/ValueSet/list-mode|4.0.1
From the FHIR Standard
Composition.section:coverage.orderedBypreferredListOrderCodes
http://hl7.org/fhir/ValueSet/list-order
From the FHIR Standard
Composition.section:coverage.emptyReasonpreferredListEmptyReasons
http://hl7.org/fhir/ValueSet/list-empty-reason
From the FHIR Standard
Composition.section:appointment.codeexamplePattern Value: LOINC Code 56446-8("Appointment summary Document")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:appointment.moderequiredListMode
http://hl7.org/fhir/ValueSet/list-mode|4.0.1
From the FHIR Standard
Composition.section:appointment.orderedBypreferredListOrderCodes
http://hl7.org/fhir/ValueSet/list-order
From the FHIR Standard
Composition.section:appointment.emptyReasonpreferredListEmptyReasons
http://hl7.org/fhir/ValueSet/list-empty-reason
From the FHIR Standard
Composition.section:carePlan.codeexamplePattern Value: LOINC Code 18776-5("Plan of care note")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:carePlan.moderequiredListMode
http://hl7.org/fhir/ValueSet/list-mode|4.0.1
From the FHIR Standard
Composition.section:carePlan.orderedBypreferredListOrderCodes
http://hl7.org/fhir/ValueSet/list-order
From the FHIR Standard
Composition.section:carePlan.emptyReasonpreferredListEmptyReasons
http://hl7.org/fhir/ValueSet/list-empty-reason
From the FHIR Standard
Composition.section:medicalDevices.codeexamplePattern Value: LOINC Code 97813-0("Implant component")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:medicalDevices.moderequiredListMode
http://hl7.org/fhir/ValueSet/list-mode|4.0.1
From the FHIR Standard
Composition.section:medicalDevices.orderedBypreferredListOrderCodes
http://hl7.org/fhir/ValueSet/list-order
From the FHIR Standard
Composition.section:medicalDevices.emptyReasonpreferredListEmptyReasons
http://hl7.org/fhir/ValueSet/list-empty-reason
From the FHIR Standard
Composition.section:attachments.codeexamplePattern Value: LOINC Code 77599-9("Additional documentation")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:attachments.moderequiredListMode
http://hl7.org/fhir/ValueSet/list-mode|4.0.1
From the FHIR Standard
Composition.section:attachments.orderedBypreferredListOrderCodes
http://hl7.org/fhir/ValueSet/list-order
From the FHIR Standard
Composition.section:attachments.emptyReasonpreferredListEmptyReasons
http://hl7.org/fhir/ValueSet/list-empty-reason
From the FHIR Standard

Constraints

IdGradePath(s)DetailsRequirements
cmp-1errorComposition.section, Composition.section:orderInformation, Composition.section:clinicalQuestion, Composition.section:coverage, Composition.section:appointment, Composition.section:carePlan, Composition.section:medicalDevices, Composition.section:attachmentsA section must contain at least one of text, entries, or sub-sections
: text.exists() or entry.exists() or section.exists()
cmp-2errorComposition.section, Composition.section:orderInformation, Composition.section:clinicalQuestion, Composition.section:coverage, Composition.section:appointment, Composition.section:carePlan, Composition.section:medicalDevices, Composition.section:attachmentsA section can only have an emptyReason if it is empty
: emptyReason.empty() or entry.empty()
dom-2errorCompositionIf the resource is contained in another resource, it SHALL NOT contain nested Resources
: contained.contained.empty()
dom-3errorCompositionIf the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
: contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4errorCompositionIf a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
: contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5errorCompositionIf a resource is contained in another resource, it SHALL NOT have a security label
: contained.meta.security.empty()
dom-6best practiceCompositionA resource should have narrative for robust management
: text.`div`.exists()
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()
text-or-sectionerrorCompositionA Composition SHALL have either text, at least one section, or both.
: text.exists() or section.exists()

This structure is derived from Composition

Summary

Mandatory: 6 elements(5 nested mandatory elements)
Must-Support: 1 element

Structures

This structure refers to these other structures:

Slices

This structure defines the following Slices:

  • The element 1 is sliced based on the value of Composition.section

Maturity: 0

Key Elements View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Composition C 0..* Composition Imaging Order Composition
Constraints: text-or-section
... meta Σ 0..1 Meta Metadata about the resource
.... security SΣ 0..* Coding Security Labels applied to this resource
Binding: All Security Labels (extensible): Security Labels from the Healthcare Privacy and Security Classification System.
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
... status ?!Σ 1..1 code Status of the Order
Binding: CompositionStatus (required): The workflow/clinical status of the composition.
... type Σ 1..1 CodeableConcept Kind of composition (LOINC if possible)
Binding: Valueset of types Clinical event (CZ) (required)
... category Σ 0..* CodeableConcept Categorization of Composition
Binding: DocumentClassValueSet (required)
... subject Σ 1..1 Reference(Patient (CZ core)) Who and/or what the composition is about
... encounter Σ 0..1 Reference(Encounter: Imaging Order (CZ)) Context that defines the Imaging Order
... date Σ 1..1 dateTime Date the order was created.
... author Σ 1..* Reference(Practitioner (CZ core) | Device: Performer/Observer (CZ)) Who and/or what authored the Imaging order
... title Σ 1..1 string Human Readable name/title
... custodian Σ 0..1 Reference(Organization (CZ core)) Organization that manages the Imaging Order
... Slices for section C 2..* BackboneElement Sections composing the Imaging Order
Slice: Unordered, Open by value:code
Constraints: cmp-1, cmp-2
.... section:All Slices Content/Rules for all slices
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... section:orderInformation C 1..* BackboneElement Order Information
Constraints: cmp-1, cmp-2
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 55115-0
....... display 1..1 string Representation defined by the system
Fixed Value: Requested imaging studies information Document
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... entry C 0..* Reference(Service Request: Imaging Order (CZ)) A reference to data that supports this section
.... section:clinicalQuestion C 1..* BackboneElement Clinical question
Constraints: cmp-1, cmp-2
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 18785-6
....... display 1..1 string Representation defined by the system
Fixed Value: Radiology Reason for study (narrative)
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... author 0..* Reference(Practitioner (CZ core) | Practitioner Role (CZ core) | Device: Performer/Observer (CZ) | Patient (CZ core) | Related Person (CZ core) | Organization (CZ core)) Who and/or what authored the section
..... text C 1..1 Narrative Text summary of the section, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... entry C 0..* Reference(Condition: Imaging Order (CZ)) A reference to data that supports this section
.... section:coverage C 0..* BackboneElement Coverage type
Constraints: cmp-1, cmp-2
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 87520-3
....... display 1..1 string Representation defined by the system
Fixed Value: Coverage type
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... entry C 0..* Reference(Coverage (CZ)) A reference to data that supports this section
.... section:appointment C 0..1 BackboneElement Appointment
Constraints: cmp-1, cmp-2
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 56446-8
....... display 1..1 string Representation defined by the system
Fixed Value: Appointment summary Document
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... entry C 0..* Reference(Appointment: Imaging Order (CZ)) A reference to data that supports this section
.... section:carePlan C 0..1 BackboneElement Care Plan
Constraints: cmp-1, cmp-2
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 18776-5
....... display 1..1 string Representation defined by the system
Fixed Value: Plan of care note
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... entry C 0..* Reference(Care plan: Imaging Order (CZ)) A reference to data that supports this section
.... section:medicalDevices C 0..* BackboneElement Medical Devices and implants
Constraints: cmp-1, cmp-2
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 97813-0
....... display 1..1 string Representation defined by the system
Fixed Value: Implant component
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... entry C 0..* Reference(Device Use Statement: Imaging Order (CZ)) A reference to data that supports this section
.... section:attachments C 0..* BackboneElement Library of attachments
Constraints: cmp-1, cmp-2
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 77599-9
....... display 1..1 string Representation defined by the system
Fixed Value: Additional documentation
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... entry C 0..* Reference(Attachment: Imaging Order (CZ)) A reference to data that supports this section

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / CodeURI
Composition.meta.securityextensibleAll Security Labels
http://hl7.org/fhir/ValueSet/security-labels
From the FHIR Standard
Composition.statusrequiredCompositionStatus
http://hl7.org/fhir/ValueSet/composition-status|4.0.1
From the FHIR Standard
Composition.typerequiredCZ_TypeClinicalEventVs(a valid code from Codesystem of Clinical Event Type)
https://hl7.cz/fhir/img-order/ValueSet/cz-typeClinicalEvent-vs
From this IG
Composition.categoryrequiredDocumentClassValueSet
http://hl7.org/fhir/ValueSet/document-classcodes
From the FHIR Standard
Composition.section:orderInformation.codeexamplePattern Value: LOINC Code 55115-0("Requested imaging studies information Document")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:clinicalQuestion.codeexamplePattern Value: LOINC Code 18785-6("Radiology Reason for study (narrative)")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:coverage.codeexamplePattern Value: LOINC Code 87520-3("Coverage type")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:appointment.codeexamplePattern Value: LOINC Code 56446-8("Appointment summary Document")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:carePlan.codeexamplePattern Value: LOINC Code 18776-5("Plan of care note")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:medicalDevices.codeexamplePattern Value: LOINC Code 97813-0("Implant component")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:attachments.codeexamplePattern Value: LOINC Code 77599-9("Additional documentation")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard

Constraints

IdGradePath(s)DetailsRequirements
cmp-1errorComposition.section, Composition.section:orderInformation, Composition.section:clinicalQuestion, Composition.section:coverage, Composition.section:appointment, Composition.section:carePlan, Composition.section:medicalDevices, Composition.section:attachmentsA section must contain at least one of text, entries, or sub-sections
: text.exists() or entry.exists() or section.exists()
cmp-2errorComposition.section, Composition.section:orderInformation, Composition.section:clinicalQuestion, Composition.section:coverage, Composition.section:appointment, Composition.section:carePlan, Composition.section:medicalDevices, Composition.section:attachmentsA section can only have an emptyReason if it is empty
: emptyReason.empty() or entry.empty()
dom-2errorCompositionIf the resource is contained in another resource, it SHALL NOT contain nested Resources
: contained.contained.empty()
dom-3errorCompositionIf the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
: contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4errorCompositionIf a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
: contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5errorCompositionIf a resource is contained in another resource, it SHALL NOT have a security label
: contained.meta.security.empty()
dom-6best practiceCompositionA resource should have narrative for robust management
: text.`div`.exists()
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()
text-or-sectionerrorCompositionA Composition SHALL have either text, at least one section, or both.
: text.exists() or section.exists()

Differential View

This structure is derived from Composition

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Composition C 0..* Composition Imaging Order Composition
Constraints: text-or-section
... meta
.... security S 0..* Coding Security Labels applied to this resource
... identifier 0..1 Identifier Order identifier
... status 1..1 code Status of the Order
... category 0..* CodeableConcept Categorization of Composition
Binding: DocumentClassValueSet (required)
... subject 1..1 Reference(Patient (CZ core)) Who and/or what the composition is about
... encounter 0..1 Reference(Encounter: Imaging Order (CZ)) Context that defines the Imaging Order
... date 1..1 dateTime Date the order was created.
... author 1..* Reference(Practitioner (CZ core) | Device: Performer/Observer (CZ)) Who and/or what authored the Imaging order
... custodian 0..1 Reference(Organization (CZ core)) Organization that manages the Imaging Order
... Slices for section 2..* BackboneElement Sections composing the Imaging Order
Slice: Unordered, Open by value:code
.... section:orderInformation 1..* BackboneElement Order Information
..... code 1..1 CodeableConcept Classification of section (recommended)
Required Pattern: At least the following
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 55115-0
....... display 1..1 string Representation defined by the system
Fixed Value: Requested imaging studies information Document
..... entry 0..* Reference(Service Request: Imaging Order (CZ)) A reference to data that supports this section
.... section:clinicalQuestion 1..* BackboneElement Clinical question
..... code 1..1 CodeableConcept Classification of section (recommended)
Required Pattern: At least the following
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 18785-6
....... display 1..1 string Representation defined by the system
Fixed Value: Radiology Reason for study (narrative)
..... author 0..* Reference(Practitioner (CZ core) | Practitioner Role (CZ core) | Device: Performer/Observer (CZ) | Patient (CZ core) | Related Person (CZ core) | Organization (CZ core)) Who and/or what authored the section
..... text 1..1 Narrative Text summary of the section, for human interpretation
..... entry 0..* Reference(Condition: Imaging Order (CZ)) A reference to data that supports this section
.... section:coverage 0..* BackboneElement Coverage type
..... code 1..1 CodeableConcept Classification of section (recommended)
Required Pattern: At least the following
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 87520-3
....... display 1..1 string Representation defined by the system
Fixed Value: Coverage type
..... entry 0..* Reference(Coverage (CZ)) A reference to data that supports this section
.... section:appointment 0..1 BackboneElement Appointment
..... code 1..1 CodeableConcept Classification of section (recommended)
Required Pattern: At least the following
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 56446-8
....... display 1..1 string Representation defined by the system
Fixed Value: Appointment summary Document
..... entry 0..* Reference(Appointment: Imaging Order (CZ)) A reference to data that supports this section
.... section:carePlan 0..1 BackboneElement Care Plan
..... code 1..1 CodeableConcept Classification of section (recommended)
Required Pattern: At least the following
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 18776-5
....... display 1..1 string Representation defined by the system
Fixed Value: Plan of care note
..... entry 0..* Reference(Care plan: Imaging Order (CZ)) A reference to data that supports this section
.... section:medicalDevices 0..* BackboneElement Medical Devices and implants
..... code 1..1 CodeableConcept Classification of section (recommended)
Required Pattern: At least the following
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 97813-0
....... display 1..1 string Representation defined by the system
Fixed Value: Implant component
..... entry 0..* Reference(Device Use Statement: Imaging Order (CZ)) A reference to data that supports this section
.... section:attachments 0..* BackboneElement Library of attachments
..... code 1..1 CodeableConcept Classification of section (recommended)
Required Pattern: At least the following
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 77599-9
....... display 1..1 string Representation defined by the system
Fixed Value: Additional documentation
..... entry 0..* Reference(Attachment: Imaging Order (CZ)) A reference to data that supports this section

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
Composition.typerequiredCZ_TypeClinicalEventVs(a valid code from Codesystem of Clinical Event Type)
https://hl7.cz/fhir/img-order/ValueSet/cz-typeClinicalEvent-vs
From this IG
Composition.categoryrequiredDocumentClassValueSet
http://hl7.org/fhir/ValueSet/document-classcodes
From the FHIR Standard

Constraints

IdGradePath(s)DetailsRequirements
text-or-sectionerrorCompositionA Composition SHALL have either text, at least one section, or both.
: text.exists() or section.exists()

Snapshot View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Composition C 0..* Composition Imaging Order Composition
Constraints: text-or-section
... id Σ 0..1 id Logical id of this artifact
... meta Σ 0..1 Meta Metadata about the resource
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
.... versionId Σ 0..1 id Version specific identifier
.... lastUpdated Σ 0..1 instant When the resource version last changed
.... source Σ 0..1 uri Identifies where the resource comes from
.... profile Σ 0..* canonical(StructureDefinition) Profiles this resource claims to conform to
.... security SΣ 0..* Coding Security Labels applied to this resource
Binding: All Security Labels (extensible): Security Labels from the Healthcare Privacy and Security Classification System.
.... tag Σ 0..* Coding Tags applied to this resource
Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
... implicitRules ?!Σ 0..1 uri A set of rules under which this content was created
... text 0..1 Narrative Text summary of the resource, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
... contained 0..* Resource Contained, inline Resources
... extension 0..* Extension Additional content defined by implementations
... modifierExtension ?! 0..* Extension Extensions that cannot be ignored
... identifier Σ 0..1 Identifier Order identifier
... status ?!Σ 1..1 code Status of the Order
Binding: CompositionStatus (required): The workflow/clinical status of the composition.
... type Σ 1..1 CodeableConcept Kind of composition (LOINC if possible)
Binding: Valueset of types Clinical event (CZ) (required)
... category Σ 0..* CodeableConcept Categorization of Composition
Binding: DocumentClassValueSet (required)
... subject Σ 1..1 Reference(Patient (CZ core)) Who and/or what the composition is about
... encounter Σ 0..1 Reference(Encounter: Imaging Order (CZ)) Context that defines the Imaging Order
... date Σ 1..1 dateTime Date the order was created.
... author Σ 1..* Reference(Practitioner (CZ core) | Device: Performer/Observer (CZ)) Who and/or what authored the Imaging order
... title Σ 1..1 string Human Readable name/title
... confidentiality Σ 0..1 code As defined by affinity domain
Binding: v3.ConfidentialityClassification (2014-03-26) (required): Codes specifying the level of confidentiality of the composition.
... attester 0..* BackboneElement Attests to accuracy of composition
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... mode 1..1 code personal | professional | legal | official
Binding: CompositionAttestationMode (required): The way in which a person authenticated a composition.
.... time 0..1 dateTime When the composition was attested
.... party 0..1 Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization) Who attested the composition
... custodian Σ 0..1 Reference(Organization (CZ core)) Organization that manages the Imaging Order
... relatesTo 0..* BackboneElement Relationships to other compositions/documents
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... code 1..1 code replaces | transforms | signs | appends
Binding: DocumentRelationshipType (required): The type of relationship between documents.
.... target[x] 1..1 Target of the relationship
..... targetIdentifier Identifier
..... targetReference Reference(Composition)
... event Σ 0..* BackboneElement The clinical service(s) being documented
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... code Σ 0..* CodeableConcept Code(s) that apply to the event being documented
Binding: ActCode (3.0.0) (example): This list of codes represents the main clinical acts being documented.
.... period Σ 0..1 Period The period covered by the documentation
.... detail Σ 0..* Reference(Resource) The event(s) being documented
... Slices for section C 2..* BackboneElement Sections composing the Imaging Order
Slice: Unordered, Open by value:code
Constraints: cmp-1, cmp-2
.... section:All Slices Content/Rules for all slices
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... title 0..1 string Label for section (e.g. for ToC)
..... code 0..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
..... author 0..* Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization) Who and/or what authored the section
..... focus 0..1 Reference(Resource) Who/what the section is about, when it is not about the subject of composition
..... text C 0..1 Narrative Text summary of the section, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... mode 0..1 code working | snapshot | changes
Binding: ListMode (required): The processing mode that applies to this section.
..... orderedBy 0..1 CodeableConcept Order of section entries
Binding: ListOrderCodes (preferred): What order applies to the items in the entry.
..... entry C 0..* Reference(Resource) A reference to data that supports this section
..... emptyReason C 0..1 CodeableConcept Why the section is empty
Binding: ListEmptyReasons (preferred): If a section is empty, why it is empty.
..... section C 0..* See section (Composition) Nested Section
.... section:orderInformation C 1..* BackboneElement Order Information
Constraints: cmp-1, cmp-2
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... title 0..1 string Label for section (e.g. for ToC)
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 55115-0
....... display 1..1 string Representation defined by the system
Fixed Value: Requested imaging studies information Document
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... author 0..* Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization) Who and/or what authored the section
..... focus 0..1 Reference(Resource) Who/what the section is about, when it is not about the subject of composition
..... text C 0..1 Narrative Text summary of the section, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... mode 0..1 code working | snapshot | changes
Binding: ListMode (required): The processing mode that applies to this section.
..... orderedBy 0..1 CodeableConcept Order of section entries
Binding: ListOrderCodes (preferred): What order applies to the items in the entry.
..... entry C 0..* Reference(Service Request: Imaging Order (CZ)) A reference to data that supports this section
..... emptyReason C 0..1 CodeableConcept Why the section is empty
Binding: ListEmptyReasons (preferred): If a section is empty, why it is empty.
..... section C 0..* See section (Composition) Nested Section
.... section:clinicalQuestion C 1..* BackboneElement Clinical question
Constraints: cmp-1, cmp-2
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... title 0..1 string Label for section (e.g. for ToC)
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 18785-6
....... display 1..1 string Representation defined by the system
Fixed Value: Radiology Reason for study (narrative)
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... author 0..* Reference(Practitioner (CZ core) | Practitioner Role (CZ core) | Device: Performer/Observer (CZ) | Patient (CZ core) | Related Person (CZ core) | Organization (CZ core)) Who and/or what authored the section
..... focus 0..1 Reference(Resource) Who/what the section is about, when it is not about the subject of composition
..... text C 1..1 Narrative Text summary of the section, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... mode 0..1 code working | snapshot | changes
Binding: ListMode (required): The processing mode that applies to this section.
..... orderedBy 0..1 CodeableConcept Order of section entries
Binding: ListOrderCodes (preferred): What order applies to the items in the entry.
..... entry C 0..* Reference(Condition: Imaging Order (CZ)) A reference to data that supports this section
..... emptyReason C 0..1 CodeableConcept Why the section is empty
Binding: ListEmptyReasons (preferred): If a section is empty, why it is empty.
..... section C 0..* See section (Composition) Nested Section
.... section:coverage C 0..* BackboneElement Coverage type
Constraints: cmp-1, cmp-2
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... title 0..1 string Label for section (e.g. for ToC)
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 87520-3
....... display 1..1 string Representation defined by the system
Fixed Value: Coverage type
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... author 0..* Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization) Who and/or what authored the section
..... focus 0..1 Reference(Resource) Who/what the section is about, when it is not about the subject of composition
..... text C 0..1 Narrative Text summary of the section, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... mode 0..1 code working | snapshot | changes
Binding: ListMode (required): The processing mode that applies to this section.
..... orderedBy 0..1 CodeableConcept Order of section entries
Binding: ListOrderCodes (preferred): What order applies to the items in the entry.
..... entry C 0..* Reference(Coverage (CZ)) A reference to data that supports this section
..... emptyReason C 0..1 CodeableConcept Why the section is empty
Binding: ListEmptyReasons (preferred): If a section is empty, why it is empty.
..... section C 0..* See section (Composition) Nested Section
.... section:appointment C 0..1 BackboneElement Appointment
Constraints: cmp-1, cmp-2
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... title 0..1 string Label for section (e.g. for ToC)
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 56446-8
....... display 1..1 string Representation defined by the system
Fixed Value: Appointment summary Document
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... author 0..* Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization) Who and/or what authored the section
..... focus 0..1 Reference(Resource) Who/what the section is about, when it is not about the subject of composition
..... text C 0..1 Narrative Text summary of the section, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... mode 0..1 code working | snapshot | changes
Binding: ListMode (required): The processing mode that applies to this section.
..... orderedBy 0..1 CodeableConcept Order of section entries
Binding: ListOrderCodes (preferred): What order applies to the items in the entry.
..... entry C 0..* Reference(Appointment: Imaging Order (CZ)) A reference to data that supports this section
..... emptyReason C 0..1 CodeableConcept Why the section is empty
Binding: ListEmptyReasons (preferred): If a section is empty, why it is empty.
..... section C 0..* See section (Composition) Nested Section
.... section:carePlan C 0..1 BackboneElement Care Plan
Constraints: cmp-1, cmp-2
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... title 0..1 string Label for section (e.g. for ToC)
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 18776-5
....... display 1..1 string Representation defined by the system
Fixed Value: Plan of care note
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... author 0..* Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization) Who and/or what authored the section
..... focus 0..1 Reference(Resource) Who/what the section is about, when it is not about the subject of composition
..... text C 0..1 Narrative Text summary of the section, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... mode 0..1 code working | snapshot | changes
Binding: ListMode (required): The processing mode that applies to this section.
..... orderedBy 0..1 CodeableConcept Order of section entries
Binding: ListOrderCodes (preferred): What order applies to the items in the entry.
..... entry C 0..* Reference(Care plan: Imaging Order (CZ)) A reference to data that supports this section
..... emptyReason C 0..1 CodeableConcept Why the section is empty
Binding: ListEmptyReasons (preferred): If a section is empty, why it is empty.
..... section C 0..* See section (Composition) Nested Section
.... section:medicalDevices C 0..* BackboneElement Medical Devices and implants
Constraints: cmp-1, cmp-2
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... title 0..1 string Label for section (e.g. for ToC)
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 97813-0
....... display 1..1 string Representation defined by the system
Fixed Value: Implant component
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... author 0..* Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization) Who and/or what authored the section
..... focus 0..1 Reference(Resource) Who/what the section is about, when it is not about the subject of composition
..... text C 0..1 Narrative Text summary of the section, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... mode 0..1 code working | snapshot | changes
Binding: ListMode (required): The processing mode that applies to this section.
..... orderedBy 0..1 CodeableConcept Order of section entries
Binding: ListOrderCodes (preferred): What order applies to the items in the entry.
..... entry C 0..* Reference(Device Use Statement: Imaging Order (CZ)) A reference to data that supports this section
..... emptyReason C 0..1 CodeableConcept Why the section is empty
Binding: ListEmptyReasons (preferred): If a section is empty, why it is empty.
..... section C 0..* See section (Composition) Nested Section
.... section:attachments C 0..* BackboneElement Library of attachments
Constraints: cmp-1, cmp-2
..... id 0..1 string Unique id for inter-element referencing
..... extension 0..* Extension Additional content defined by implementations
..... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
..... title 0..1 string Label for section (e.g. for ToC)
..... code 1..1 CodeableConcept Classification of section (recommended)
Binding: DocumentSectionCodes (example): Classification of a section of a composition/document.
Required Pattern: At least the following
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
...... coding 1..* Coding Code defined by a terminology system
Fixed Value: (complex)
....... id 0..1 string Unique id for inter-element referencing
....... extension 0..* Extension Additional content defined by implementations
....... system 1..1 uri Identity of the terminology system
Fixed Value: http://loinc.org
....... version 0..1 string Version of the system - if relevant
....... code 1..1 code Symbol in syntax defined by the system
Fixed Value: 77599-9
....... display 1..1 string Representation defined by the system
Fixed Value: Additional documentation
....... userSelected 0..1 boolean If this coding was chosen directly by the user
...... text 0..1 string Plain text representation of the concept
..... author 0..* Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization) Who and/or what authored the section
..... focus 0..1 Reference(Resource) Who/what the section is about, when it is not about the subject of composition
..... text C 0..1 Narrative Text summary of the section, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... mode 0..1 code working | snapshot | changes
Binding: ListMode (required): The processing mode that applies to this section.
..... orderedBy 0..1 CodeableConcept Order of section entries
Binding: ListOrderCodes (preferred): What order applies to the items in the entry.
..... entry C 0..* Reference(Attachment: Imaging Order (CZ)) A reference to data that supports this section
..... emptyReason C 0..1 CodeableConcept Why the section is empty
Binding: ListEmptyReasons (preferred): If a section is empty, why it is empty.
..... section C 0..* See section (Composition) Nested Section

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / CodeURI
Composition.meta.securityextensibleAll Security Labels
http://hl7.org/fhir/ValueSet/security-labels
From the FHIR Standard
Composition.meta.tagexampleCommonTags
http://hl7.org/fhir/ValueSet/common-tags
From the FHIR Standard
Composition.languagepreferredCommonLanguages
http://hl7.org/fhir/ValueSet/languages
From the FHIR Standard
Additional Bindings Purpose
AllLanguages Max Binding
Composition.statusrequiredCompositionStatus
http://hl7.org/fhir/ValueSet/composition-status|4.0.1
From the FHIR Standard
Composition.typerequiredCZ_TypeClinicalEventVs(a valid code from Codesystem of Clinical Event Type)
https://hl7.cz/fhir/img-order/ValueSet/cz-typeClinicalEvent-vs
From this IG
Composition.categoryrequiredDocumentClassValueSet
http://hl7.org/fhir/ValueSet/document-classcodes
From the FHIR Standard
Composition.confidentialityrequiredv3.ConfidentialityClassification
http://terminology.hl7.org/ValueSet/v3-ConfidentialityClassification|2014-03-26
From the FHIR Standard
Composition.attester.moderequiredCompositionAttestationMode
http://hl7.org/fhir/ValueSet/composition-attestation-mode|4.0.1
From the FHIR Standard
Composition.relatesTo.coderequiredDocumentRelationshipType
http://hl7.org/fhir/ValueSet/document-relationship-type|4.0.1
From the FHIR Standard
Composition.event.codeexampleActCode
http://terminology.hl7.org/ValueSet/v3-ActCode|3.0.0
Composition.section.codeexampleDocumentSectionCodes
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section.moderequiredListMode
http://hl7.org/fhir/ValueSet/list-mode|4.0.1
From the FHIR Standard
Composition.section.orderedBypreferredListOrderCodes
http://hl7.org/fhir/ValueSet/list-order
From the FHIR Standard
Composition.section.emptyReasonpreferredListEmptyReasons
http://hl7.org/fhir/ValueSet/list-empty-reason
From the FHIR Standard
Composition.section:orderInformation.codeexamplePattern Value: LOINC Code 55115-0("Requested imaging studies information Document")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:orderInformation.moderequiredListMode
http://hl7.org/fhir/ValueSet/list-mode|4.0.1
From the FHIR Standard
Composition.section:orderInformation.orderedBypreferredListOrderCodes
http://hl7.org/fhir/ValueSet/list-order
From the FHIR Standard
Composition.section:orderInformation.emptyReasonpreferredListEmptyReasons
http://hl7.org/fhir/ValueSet/list-empty-reason
From the FHIR Standard
Composition.section:clinicalQuestion.codeexamplePattern Value: LOINC Code 18785-6("Radiology Reason for study (narrative)")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:clinicalQuestion.moderequiredListMode
http://hl7.org/fhir/ValueSet/list-mode|4.0.1
From the FHIR Standard
Composition.section:clinicalQuestion.orderedBypreferredListOrderCodes
http://hl7.org/fhir/ValueSet/list-order
From the FHIR Standard
Composition.section:clinicalQuestion.emptyReasonpreferredListEmptyReasons
http://hl7.org/fhir/ValueSet/list-empty-reason
From the FHIR Standard
Composition.section:coverage.codeexamplePattern Value: LOINC Code 87520-3("Coverage type")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:coverage.moderequiredListMode
http://hl7.org/fhir/ValueSet/list-mode|4.0.1
From the FHIR Standard
Composition.section:coverage.orderedBypreferredListOrderCodes
http://hl7.org/fhir/ValueSet/list-order
From the FHIR Standard
Composition.section:coverage.emptyReasonpreferredListEmptyReasons
http://hl7.org/fhir/ValueSet/list-empty-reason
From the FHIR Standard
Composition.section:appointment.codeexamplePattern Value: LOINC Code 56446-8("Appointment summary Document")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:appointment.moderequiredListMode
http://hl7.org/fhir/ValueSet/list-mode|4.0.1
From the FHIR Standard
Composition.section:appointment.orderedBypreferredListOrderCodes
http://hl7.org/fhir/ValueSet/list-order
From the FHIR Standard
Composition.section:appointment.emptyReasonpreferredListEmptyReasons
http://hl7.org/fhir/ValueSet/list-empty-reason
From the FHIR Standard
Composition.section:carePlan.codeexamplePattern Value: LOINC Code 18776-5("Plan of care note")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:carePlan.moderequiredListMode
http://hl7.org/fhir/ValueSet/list-mode|4.0.1
From the FHIR Standard
Composition.section:carePlan.orderedBypreferredListOrderCodes
http://hl7.org/fhir/ValueSet/list-order
From the FHIR Standard
Composition.section:carePlan.emptyReasonpreferredListEmptyReasons
http://hl7.org/fhir/ValueSet/list-empty-reason
From the FHIR Standard
Composition.section:medicalDevices.codeexamplePattern Value: LOINC Code 97813-0("Implant component")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:medicalDevices.moderequiredListMode
http://hl7.org/fhir/ValueSet/list-mode|4.0.1
From the FHIR Standard
Composition.section:medicalDevices.orderedBypreferredListOrderCodes
http://hl7.org/fhir/ValueSet/list-order
From the FHIR Standard
Composition.section:medicalDevices.emptyReasonpreferredListEmptyReasons
http://hl7.org/fhir/ValueSet/list-empty-reason
From the FHIR Standard
Composition.section:attachments.codeexamplePattern Value: LOINC Code 77599-9("Additional documentation")
http://hl7.org/fhir/ValueSet/doc-section-codes
From the FHIR Standard
Composition.section:attachments.moderequiredListMode
http://hl7.org/fhir/ValueSet/list-mode|4.0.1
From the FHIR Standard
Composition.section:attachments.orderedBypreferredListOrderCodes
http://hl7.org/fhir/ValueSet/list-order
From the FHIR Standard
Composition.section:attachments.emptyReasonpreferredListEmptyReasons
http://hl7.org/fhir/ValueSet/list-empty-reason
From the FHIR Standard

Constraints

IdGradePath(s)DetailsRequirements
cmp-1errorComposition.section, Composition.section:orderInformation, Composition.section:clinicalQuestion, Composition.section:coverage, Composition.section:appointment, Composition.section:carePlan, Composition.section:medicalDevices, Composition.section:attachmentsA section must contain at least one of text, entries, or sub-sections
: text.exists() or entry.exists() or section.exists()
cmp-2errorComposition.section, Composition.section:orderInformation, Composition.section:clinicalQuestion, Composition.section:coverage, Composition.section:appointment, Composition.section:carePlan, Composition.section:medicalDevices, Composition.section:attachmentsA section can only have an emptyReason if it is empty
: emptyReason.empty() or entry.empty()
dom-2errorCompositionIf the resource is contained in another resource, it SHALL NOT contain nested Resources
: contained.contained.empty()
dom-3errorCompositionIf the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
: contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4errorCompositionIf a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
: contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5errorCompositionIf a resource is contained in another resource, it SHALL NOT have a security label
: contained.meta.security.empty()
dom-6best practiceCompositionA resource should have narrative for robust management
: text.`div`.exists()
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()
text-or-sectionerrorCompositionA Composition SHALL have either text, at least one section, or both.
: text.exists() or section.exists()

This structure is derived from Composition

Summary

Mandatory: 6 elements(5 nested mandatory elements)
Must-Support: 1 element

Structures

This structure refers to these other structures:

Slices

This structure defines the following Slices:

  • The element 1 is sliced based on the value of Composition.section

Maturity: 0

 

Other representations of profile: CSV, Excel, Schematron