Union of https://profiles.ihe.net/RAD/MADO/StructureDefinition/MadoComposition and https://profiles.ihe.net/RAD/MADO/StructureDefinition/MadoComposition

This is the set of resources that conform to either of the profiles MADO Composition (https://profiles.ihe.net/RAD/MADO/StructureDefinition/MadoComposition) and MADO Composition (https://profiles.ihe.net/RAD/MADO/StructureDefinition/MadoComposition). E.g. what you have to deal with if you get resources conforming to one of them

Structure

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Composition 0..*A set of resources composed into a single coherent clinical statement with clinical attestation
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: ?? (preferred): A human language.
... text S1..1NarrativeA human readable narrative that contains information about the manifest.
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
.... extension 0..*ExtensionAdditional content defined by implementations
.... status 1..1codegenerated | extensions | additional | empty
Binding: ?? (required)
.... div C1..1xhtmlLimited xhtml content
Constraints: txt-1, txt-2
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier SΣ1..1IdentifierAn OID according for a FHIR-Based formatted Imaging Study Manifest. The OID is structured according to the DICOM UI value representation. In the case that a DICOM KOS manifest is present, this field will hold the same value as the SOP Instance UID of the corresponding translated DICOM KOS manifest.
... status ?!Σ1..1codepreliminary | final | amended | entered-in-error
Binding: ?? (required): The workflow/clinical status of the composition.
... type SΣ1..1CodeableConceptKind of document (LOINC if possible), see section 6.X.6 of volume 3.
Binding: ?? (preferred): Type of a composition.
... category SΣ0..*CodeableConceptCategorization of document, see section 6.X.6 of volume 3.
Binding: ?? (example): High-level kind of a clinical document at a macro level.
... subject SΣ1..1Reference(MADO Patient | #sd-6-MadoPatient-MadoPatient)Who and/or what the composition is about
... encounter Σ0..1Reference(Encounter)Context of the Composition
... date SΣ1..1dateTimeWhen the manifest was created.
... author Σ2..*Reference(Practitioner | PractitionerRole | Device | Patient | RelatedPerson | Organization)Who and/or what authored the document (i.e. manifest)
... title SΣ1..1stringHuman readable title to display for the manifest.
... confidentiality Σ0..1codeAs defined by affinity domain
Binding: ?? (required): Codes specifying the level of confidentiality of the composition.
... attester 0..*BackboneElementAttests to accuracy of composition
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... mode 1..1codepersonal | professional | legal | official
Binding: ?? (required): The way in which a person authenticated a composition.
.... time 0..1dateTimeWhen the composition was attested
.... party 0..1Reference(Patient | RelatedPerson | Practitioner | PractitionerRole | Organization)Who attested the composition
... custodian Σ0..1Reference(Organization)The organization that is the custodian of the manifest.
... relatesTo 0..*BackboneElementRelationships to other compositions/documents
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... code 1..1codereplaces | transforms | signs | appends
Binding: ?? (required): The type of relationship between documents.
.... target[x] 1..1Target of the relationship
..... targetIdentifierIdentifier
..... targetReferenceReference(Composition)
... event Σ1..*BackboneElementThe clinical service(s) being documented
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... code Σ0..*CodeableConceptCode(s) that apply to the event being documented
Binding: ?? (example): This list of codes represents the main clinical acts being documented.
.... period Σ0..1PeriodThe period covered by the documentation
.... detail Σ0..*Reference(Resource)The event(s) being documented
... section SC0..*BackboneElementOptionally, one or more sections. Each section provides information on a series in the study.
Constraints: cmp-1, cmp-2
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... title 0..1stringLabel for section (e.g. for ToC)
.... code 0..1CodeableConceptClassification of section (recommended)
Binding: ?? (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..1Reference(Resource)Who/what the section is about, when it is not about the subject of composition
.... text S1..1NarrativeA human readable narrative that contains the information about the section. This narrative could contain information like: the series instance UID, the series description, the number of instances in the series, and/or the modality.
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
..... extension 0..*ExtensionAdditional content defined by implementations
..... status 1..1codegenerated | extensions | additional | empty
Binding: ?? (required)
..... div C1..1xhtmlLimited xhtml content
Constraints: txt-1, txt-2
.... mode 0..1codeworking | snapshot | changes
Binding: ?? (required): The processing mode that applies to this section.
.... orderedBy 0..1CodeableConceptOrder of section entries
Binding: ?? (preferred): What order applies to the items in the entry.
.... entry 0..*Reference(Resource)A reference to data that supports this section
.... emptyReason 0..1CodeableConceptWhy the section is empty
Binding: ?? (preferred): If a section is empty, why it is empty.
.... section 0..*Nested Section

doco Documentation for this format