Union of http://hl7.org/fhir/us/resp-net/StructureDefinition/resp-net-composition and http://hl7.org/fhir/us/resp-net/StructureDefinition/resp-net-composition

This is the set of resources that conform to either of the profiles RESP-NET Composition (http://hl7.org/fhir/us/resp-net/StructureDefinition/resp-net-composition) and RESP-NET Composition (http://hl7.org/fhir/us/resp-net/StructureDefinition/resp-net-composition). E.g. what you have to deal with if you get resources conforming to one of them

Structure

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Composition S0..*Resp-net Composition Profile
... 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.
... contained 0..*ResourceContained, inline Resources
... extension 0..*Extensionleft: Additional content defined by implementations; right: Extension
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier SΣ1..1IdentifierRESP-NET Composition identifier
... status ?!SΣ1..1codepreliminary | final | amended | entered-in-error
Binding: ?? (required): The workflow/clinical status of the composition.
... type SΣ1..1CodeableConceptRESP-NET Report
Binding: ?? (preferred): Type of a composition.
... category Σ0..*CodeableConceptCategorization of Composition
Binding: ?? (example): High-level kind of a clinical document at a macro level.
... subject SΣ1..1Reference(US Public Health Patient)Patient who is the subject of the report.
... encounter SΣ1..1Reference(US Public Health Encounter)Encounter related to the public health event
... date SΣ1..1dateTimeComposition editing time
... author SΣ1..*Reference(US Core PractitionerRole Profile(4.0.0) | US Core Practitioner Profile(4.0.0) | US Core Organization Profile(4.0.0) | Device | #sd-us-core-practitionerrole-us-core-practitionerrole)The author(s) of the document
... title SΣ1..1stringHuman Readable name/title
... 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)Organization which maintains the composition
... 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 Σ0..*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..*BackboneElementComposition is broken into sections
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 0..1NarrativeText 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..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