Composition
Resource Structure
| CompositionUvIps (Composition) | C | Composition | |
| id | Σ | 0..1 | string |
| meta | Σ | 0..1 | Meta |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| versionId | Σ | 0..1 | id |
| lastUpdated | Σ | 0..1 | instant |
| source | Σ | 0..1 | uri |
| profile | SO Σ | 0..* | canonical(StructureDefinition) |
| security | Σ | 0..* | CodingBinding |
| tag | Σ | 0..* | Coding |
| implicitRules | Σ ?! | 0..1 | uri |
| language | 0..1 | codeBinding | |
| text | SO | 0..1 | Narrative |
| contained | 0..* | Resource | |
| extension | C | 0..* | Extension |
| modifierExtension | ?! C | 0..* | Extension |
| identifier | SO Σ | 0..1 | Identifier |
| status | SO Σ ?! | 1..1 | codeBinding |
| type | SO Σ | 1..1 | CodeableConceptIPSBindingPattern |
| category | Σ | 0..* | CodeableConcept |
| subject | SO Σ C | 1..1 | Reference(PatientUvIps) |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| reference | SO Σ C | 1..1 | string |
| type | Σ | 0..1 | uriBinding |
| identifier | Σ | 0..1 | Identifier |
| display | Σ | 0..1 | string |
| encounter | Σ C | 0..1 | Reference(Encounter) |
| date | SO Σ | 1..1 | dateTime |
| author | SO Σ C | 1..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| title | SO Σ | 1..1 | string |
| confidentiality | Σ | 0..1 | codeBinding |
| attester | SO | 0..* | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| mode | SO | 1..1 | codeBinding |
| time | SO | 0..1 | dateTime |
| party | SO C | 0..1 | Reference(Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| custodian | SO Σ C | 0..1 | Reference(Organization) |
| relatesTo | 0..* | BackboneElement | |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| code | 1..1 | codeBinding | |
| target[x] | 1..1 | ||
| targetIdentifier | Identifier | ||
| targetReference | Reference(Composition | CompositionUvIps) | ||
| event | Σ | 0..* | BackboneElement |
| (All Slices) | |||
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| code | Σ | 0..* | CodeableConcept |
| period | Σ C | 0..1 | Period |
| detail | Σ C | 0..* | Reference(Resource) |
| careProvisioningEvent | SO Σ | 0..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| code | SO Σ | 1..1 | CodeableConceptPattern |
| period | SO Σ C | 0..1 | Period |
| detail | Σ C | 0..* | Reference(Resource) |
| section | SO C | 3..* | BackboneElement |
| (All Slices) | |||
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| section-note | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| title | SO | 1..1 | string |
| code | SO | 1..1 | CodeableConcept |
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| focus | C | 0..1 | Reference(Resource) |
| text | SO C | 1..1 | Narrative |
| mode | 0..1 | codeBinding | |
| orderedBy | 0..1 | CodeableConceptBinding | |
| entry | C | 0..* | Reference(Resource) |
| emptyReason | C | 0..1 | CodeableConceptBinding |
| section | C | 0..0 | see (section) |
| sectionProblems | SO C | 1..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| section-note | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| title | SO | 1..1 | string |
| code | SO | 1..1 | CodeableConceptPattern |
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| focus | C | 0..1 | Reference(Resource) |
| text | SO C | 1..1 | Narrative |
| mode | 0..1 | codeBinding | |
| orderedBy | 0..1 | CodeableConceptBinding | |
| entry | C | 0..* | Reference(Condition | DocumentReference) |
| problem | SO C | 0..* | Reference(ConditionUvIps) |
| emptyReason | SO C | 0..1 | CodeableConceptBinding |
| section | C | 0..0 | see (section) |
| sectionAllergies | SO C | 1..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| section-note | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| title | SO | 1..1 | string |
| code | SO | 1..1 | CodeableConceptPattern |
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| focus | C | 0..1 | Reference(Resource) |
| text | SO C | 1..1 | Narrative |
| mode | 0..1 | codeBinding | |
| orderedBy | 0..1 | CodeableConceptBinding | |
| entry | C | 0..* | Reference(AllergyIntolerance | DocumentReference) |
| allergyOrIntolerance | SO C | 0..* | Reference(AllergyIntoleranceUvIps) |
| emptyReason | SO C | 0..1 | CodeableConceptBinding |
| section | C | 0..0 | see (section) |
| sectionMedications | SO C | 1..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| section-note | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| title | SO | 1..1 | string |
| code | SO | 1..1 | CodeableConceptPattern |
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| focus | C | 0..1 | Reference(Resource) |
| text | SO C | 1..1 | Narrative |
| mode | 0..1 | codeBinding | |
| orderedBy | 0..1 | CodeableConceptBinding | |
| entry | C | 0..* | Reference(DocumentReference | MedicationAdministration | MedicationDispense | MedicationRequest | MedicationStatement) |
| medicationStatementOrRequest | SO C | 0..* | Reference(MedicationRequestIPS | MedicationStatementIPS) |
| emptyReason | SO C | 0..1 | CodeableConceptBinding |
| section | C | 0..0 | see (section) |
| sectionImmunizations | SO C | 0..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| section-note | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| title | SO | 1..1 | string |
| code | SO | 1..1 | CodeableConceptPattern |
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| focus | C | 0..1 | Reference(Resource) |
| text | SO C | 1..1 | Narrative |
| mode | 0..1 | codeBinding | |
| orderedBy | 0..1 | CodeableConceptBinding | |
| entry | C | 0..* | Reference(DocumentReference | Immunization) |
| immunization | SO C | 0..* | Reference(ImmunizationUvIps) |
| emptyReason | C | 0..1 | CodeableConceptBinding |
| section | C | 0..0 | see (section) |
| sectionResults | SO C | 0..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| section-note | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| title | SO | 1..1 | string |
| code | SO | 1..1 | CodeableConceptPattern |
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| focus | C | 0..1 | Reference(Resource) |
| text | SO C | 1..1 | Narrative |
| mode | 0..1 | codeBinding | |
| orderedBy | 0..1 | CodeableConceptBinding | |
| entry | C | 0..* | Reference(DiagnosticReport | DocumentReference | Observation) |
| results-observation-laboratory-pathology | SO C | 0..* | Reference(ObservationResultsLaboratoryPathologyUvIps) |
| results-observation-radiology | SO C | 0..* | Reference(ObservationResultsRadiologyUvIps) |
| results-diagnosticReport | SO C | 0..* | Reference(DiagnosticReportUvIps) |
| emptyReason | C | 0..1 | CodeableConceptBinding |
| section | C | 0..0 | see (section) |
| sectionProceduresHx | SO C | 0..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| section-note | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| title | SO | 1..1 | string |
| code | SO | 1..1 | CodeableConceptPattern |
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| focus | C | 0..1 | Reference(Resource) |
| text | SO C | 1..1 | Narrative |
| mode | 0..1 | codeBinding | |
| orderedBy | 0..1 | CodeableConceptBinding | |
| entry | C | 0..* | Reference(DocumentReference | Procedure) |
| procedure | SO C | 0..* | Reference(ProcedureUvIps) |
| emptyReason | C | 0..1 | CodeableConceptBinding |
| section | C | 0..0 | see (section) |
| sectionMedicalDevices | SO C | 0..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| section-note | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| title | SO | 1..1 | string |
| code | SO | 1..1 | CodeableConceptPattern |
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| focus | C | 0..1 | Reference(Resource) |
| text | SO C | 1..1 | Narrative |
| mode | 0..1 | codeBinding | |
| orderedBy | 0..1 | CodeableConceptBinding | |
| entry | C | 0..* | Reference(DeviceUseStatement | DocumentReference) |
| deviceStatement | SO C | 0..* | Reference(DeviceUseStatementUvIps) |
| emptyReason | C | 0..1 | CodeableConceptBinding |
| section | C | 0..0 | see (section) |
| sectionAdvanceDirectives | SO C | 0..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| section-note | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| title | SO | 1..1 | string |
| code | SO | 1..1 | CodeableConceptPattern |
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| focus | C | 0..1 | Reference(Resource) |
| text | SO C | 1..1 | Narrative |
| mode | 0..1 | codeBinding | |
| orderedBy | 0..1 | CodeableConceptBinding | |
| entry | C | 0..* | Reference(Consent | DocumentReference) |
| advanceDirectivesConsent | C | 0..* | Reference(Consent) |
| emptyReason | C | 0..1 | CodeableConceptBinding |
| section | C | 0..0 | see (section) |
| sectionAlerts | SO C | 0..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| section-note | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| title | SO | 1..1 | string |
| code | SO | 1..1 | CodeableConceptPattern |
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| focus | C | 0..1 | Reference(Resource) |
| text | SO C | 1..1 | Narrative |
| mode | 0..1 | codeBinding | |
| orderedBy | 0..1 | CodeableConceptBinding | |
| entry | C | 0..* | Reference(DocumentReference | Flag) |
| alertsFlag | C | 0..* | Reference(FlagAlertUvIps) |
| emptyReason | C | 0..1 | CodeableConceptBinding |
| section | C | 0..0 | see (section) |
| sectionFunctionalStatus | SO C | 0..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| section-note | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| title | SO | 1..1 | string |
| code | SO | 1..1 | CodeableConceptPattern |
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| focus | C | 0..1 | Reference(Resource) |
| text | SO C | 1..1 | Narrative |
| mode | 0..1 | codeBinding | |
| orderedBy | 0..1 | CodeableConceptBinding | |
| entry | C | 0..* | Reference(ClinicalImpression | Condition | DocumentReference) |
| disability | C | 0..* | Reference(ConditionUvIps) |
| functionalAssessment | C | 0..* | Reference(ClinicalImpression) |
| emptyReason | C | 0..1 | CodeableConceptBinding |
| section | C | 0..0 | see (section) |
| sectionPastProblems | SO C | 0..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| section-note | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| title | SO | 1..1 | string |
| code | SO | 1..1 | CodeableConceptPattern |
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| focus | C | 0..1 | Reference(Resource) |
| text | SO C | 1..1 | Narrative |
| mode | 0..1 | codeBinding | |
| orderedBy | 0..1 | CodeableConceptBinding | |
| entry | C | 0..* | Reference(Condition | DocumentReference) |
| pastProblem | C | 0..* | Reference(ConditionUvIps) |
| emptyReason | C | 0..1 | CodeableConceptBinding |
| section | C | 0..0 | see (section) |
| sectionPregnancyHx | SO C | 0..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| section-note | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| title | SO | 1..1 | string |
| code | SO | 1..1 | CodeableConceptPattern |
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| focus | C | 0..1 | Reference(Resource) |
| text | SO C | 1..1 | Narrative |
| mode | 0..1 | codeBinding | |
| orderedBy | 0..1 | CodeableConceptBinding | |
| entry | C | 0..* | Reference(DocumentReference | Observation) |
| pregnancyStatus | C | 0..* | Reference(ObservationPregnancyStatusUvIps) |
| pregnancyOutcome | C | 0..* | Reference(ObservationPregnancyOutcomeUvIps) |
| emptyReason | C | 0..1 | CodeableConceptBinding |
| section | C | 0..0 | see (section) |
| sectionPatientStory | SO C | 0..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| section-note | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| title | SO | 1..1 | string |
| code | SO | 1..1 | CodeableConceptPattern |
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| focus | C | 0..1 | Reference(Resource) |
| text | SO C | 1..1 | Narrative |
| mode | 0..1 | codeBinding | |
| orderedBy | 0..1 | CodeableConceptBinding | |
| entry | C | 0..* | Reference(Resource) |
| emptyReason | C | 0..1 | CodeableConceptBinding |
| section | C | 0..0 | see (section) |
| sectionPlanOfCare | SO C | 0..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| section-note | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| title | SO | 1..1 | string |
| code | SO | 1..1 | CodeableConceptPattern |
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| focus | C | 0..1 | Reference(Resource) |
| text | SO C | 1..1 | Narrative |
| mode | 0..1 | codeBinding | |
| orderedBy | 0..1 | CodeableConceptBinding | |
| entry | C | 0..* | Reference(CarePlan | DocumentReference | ImmunizationRecommendation) |
| carePlan | C | 0..* | Reference(CarePlan) |
| immunizationRecommendation | C | 0..* | Reference(ImmunizationRecommendation) |
| emptyReason | C | 0..1 | CodeableConceptBinding |
| section | C | 0..0 | see (section) |
| sectionSocialHistory | SO C | 0..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| section-note | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| title | SO | 1..1 | string |
| code | SO | 1..1 | CodeableConceptPattern |
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| focus | C | 0..1 | Reference(Resource) |
| text | SO C | 1..1 | Narrative |
| mode | 0..1 | codeBinding | |
| orderedBy | 0..1 | CodeableConceptBinding | |
| entry | C | 0..* | Reference(DocumentReference | Observation) |
| smokingTobaccoUse | C | 0..1 | Reference(ObservationTobaccoUseUvIps) |
| alcoholUse | C | 0..1 | Reference(ObservationAlcoholUseUvIps) |
| emptyReason | C | 0..1 | CodeableConceptBinding |
| section | C | 0..0 | see (section) |
| sectionVitalSigns | SO C | 0..1 | BackboneElement |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| section-note | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| title | SO | 1..1 | string |
| code | SO | 1..1 | CodeableConceptPattern |
| author | C | 0..* | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) |
| focus | C | 0..1 | Reference(Resource) |
| text | SO C | 1..1 | Narrative |
| mode | 0..1 | codeBinding | |
| orderedBy | 0..1 | CodeableConceptBinding | |
| entry | C | 0..* | Reference(DocumentReference | Observation) |
| vitalSign | C | 0..* | Reference(observation-vitalsigns) |
| emptyReason | C | 0..1 | CodeableConceptBinding |
| section | C | 0..0 | see (section) |
Detailed Information
| Composition | |||||||||||
| Short | International Patient Summary composition | ||||||||||
| Definition | International Patient Summary composition. A composition is a set of healthcare-related information that is assembled together into a single logical document that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. While a Composition defines the structure, it does not actually contain the content: rather the full content of a document is contained in a Bundle, of which the Composition is the first resource contained. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Comments | While the focus of this specification is on patient-specific clinical statements, this resource can also apply to other healthcare-related statements such as study protocol designs, healthcare invoices and other activities that are not necessarily patient-specific or clinical. | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.id | |||||||||||
| Short | Logical id of this artifact | ||||||||||
| Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Summary | True | ||||||||||
| Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | ||||||||||
| Composition.meta | |||||||||||
| Short | Metadata about the resource | ||||||||||
| Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Meta | ||||||||||
| Summary | True | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.meta.id | |||||||||||
| Short | Unique id for inter-element referencing | ||||||||||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Mappings |
| ||||||||||
| Composition.meta.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.meta.versionId | |||||||||||
| Short | Version specific identifier | ||||||||||
| Definition | The version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | id | ||||||||||
| Summary | True | ||||||||||
| Comments | The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.meta.lastUpdated | |||||||||||
| Short | When the resource version last changed | ||||||||||
| Definition | When the resource last changed - e.g. when the version changed. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | instant | ||||||||||
| Summary | True | ||||||||||
| Comments | This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a read interaction. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.meta.source | |||||||||||
| Short | Identifies where the resource comes from | ||||||||||
| Definition | A uri that identifies the source system of the resource. This provides a minimal amount of Provenance information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | uri | ||||||||||
| Summary | True | ||||||||||
| Comments | In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.meta.profile | |||||||||||
| Short | The conformance of this Composition to a specific IPS version. | ||||||||||
| Definition | The conformance of this Composition to a specific version of the IPS (e.g. http://hl7.org/fhir/uv/ips/StructureDefinition/Composition-uv-ips|2.0.0 for 2.0.0) | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | canonical(StructureDefinition) | ||||||||||
| Must Support | True | ||||||||||
| Summary | True | ||||||||||
| Comments | It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.meta.security | |||||||||||
| Short | Security Labels applied to this resource | ||||||||||
| Definition | Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Coding | ||||||||||
| Binding | Security Labels from the Healthcare Privacy and Security Classification System. | ||||||||||
| Summary | True | ||||||||||
| Comments | The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.meta.tag | |||||||||||
| Short | Tags applied to this resource | ||||||||||
| Definition | Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Coding | ||||||||||
| Binding | Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones". | ||||||||||
| Summary | True | ||||||||||
| Comments | The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.implicitRules | |||||||||||
| Short | A set of rules under which this content was created | ||||||||||
| Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | uri | ||||||||||
| Modifier | True | ||||||||||
| Summary | True | ||||||||||
| Comments | Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.language | |||||||||||
| Short | Language of the resource content | ||||||||||
| Definition | The base language in which the resource is written. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | code | ||||||||||
| Binding | A human language.
| ||||||||||
| Comments | Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.text | |||||||||||
| Short | Text summary of the resource, for human interpretation | ||||||||||
| Definition | A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Narrative | ||||||||||
| Must Support | True | ||||||||||
| Alias | narrative, html, xhtml, display | ||||||||||
| Comments | Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.contained | |||||||||||
| Short | Contained, inline Resources | ||||||||||
| Definition | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Resource | ||||||||||
| Alias | inline resources, anonymous resources, contained resources | ||||||||||
| Comments | This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels. | ||||||||||
| Mappings |
| ||||||||||
| Composition.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.modifierExtension | |||||||||||
| Short | Extensions that cannot be ignored | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Modifier | True | ||||||||||
| Alias | extensions, user content | ||||||||||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.identifier | |||||||||||
| Short | Version-independent identifier for the Composition | ||||||||||
| Definition | A version-independent identifier for the Composition. This identifier stays constant as the composition is changed over time. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Identifier | ||||||||||
| Must Support | True | ||||||||||
| Summary | True | ||||||||||
| Comments | Similar to ClinicalDocument/setId in CDA. See discussion in resource definition for how these relate. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.status | |||||||||||
| Short | preliminary | final | amended | entered-in-error | ||||||||||
| Definition | The workflow/clinical status of this composition. The status is a marker for the clinical standing of the document. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | code | ||||||||||
| Binding | The workflow/clinical status of the composition. | ||||||||||
| Must Support | True | ||||||||||
| Modifier | True | ||||||||||
| Summary | True | ||||||||||
| Requirements | Need to be able to mark interim, amended, or withdrawn compositions or documents. | ||||||||||
| Comments | If a composition is marked as withdrawn, the compositions/documents in the series, or data from the composition or document series, should never be displayed to a user without being clearly marked as untrustworthy. The flag "entered-in-error" is why this element is labeled as a modifier of other elements. Some reporting work flows require that the original narrative of a final document never be altered; instead, only new narrative can be added. The composition resource has no explicit status for explicitly noting whether this business rule is in effect. This would be handled by an extension if required. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.type | |||||||||||
| Short | Kind of composition ("Patient Summary") | ||||||||||
| Definition | Specifies that this composition refers to a Patient Summary (Loinc "60591-5") | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | CodeableConceptIPS | ||||||||||
| Binding | Type of a composition. | ||||||||||
| Must Support | True | ||||||||||
| Summary | True | ||||||||||
| Requirements | Key metadata element describing the composition, used in searching/filtering. | ||||||||||
| Comments | Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Pattern | {
"coding": [
{
"system": "http://loinc.org",
"code": "60591-5"
}
]
} | ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.category | |||||||||||
| Short | Categorization of Composition | ||||||||||
| Definition | A categorization for the type of the composition - helps for indexing and searching. This may be implied by or derived from the code specified in the Composition Type. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | High-level kind of a clinical document at a macro level. | ||||||||||
| Summary | True | ||||||||||
| Requirements | Helps humans to assess whether the composition is of interest when viewing an index of compositions or documents. | ||||||||||
| Comments | This is a metadata field from XDS/MHD. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.subject | |||||||||||
| Short | Who and/or what the composition is about | ||||||||||
| Definition | Who or what the composition is about. In general a composition can be about a person, (patient or healthcare practitioner), a device (e.g. a machine) or even a group of subjects (such as a document about a herd of livestock, or a set of patients that share a common exposure). For the IPS the subject is always the patient. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | Reference(PatientUvIps) | ||||||||||
| Must Support | True | ||||||||||
| Summary | True | ||||||||||
| Requirements | Essential metadata for searching for the composition. Identifies who and/or what the composition/document is about. | ||||||||||
| Comments | For clinical documents, this is usually the patient. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.subject.id | |||||||||||
| Short | Unique id for inter-element referencing | ||||||||||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Mappings |
| ||||||||||
| Composition.subject.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.subject.reference | |||||||||||
| Short | Literal reference, Relative, internal or absolute URL | ||||||||||
| Definition | A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | string | ||||||||||
| Must Support | True | ||||||||||
| Summary | True | ||||||||||
| Comments | Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, ref-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.subject.type | |||||||||||
| Short | Type the reference refers to (e.g. "Patient") | ||||||||||
| Definition | The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | uri | ||||||||||
| Binding | Aa resource (or, for logical models, the URI of the logical model). | ||||||||||
| Summary | True | ||||||||||
| Comments | This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.subject.identifier | |||||||||||
| Short | Logical reference, when literal reference is not known | ||||||||||
| Definition | An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Identifier | ||||||||||
| Summary | True | ||||||||||
| Comments | When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any). | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.subject.display | |||||||||||
| Short | Text alternative for the resource | ||||||||||
| Definition | Plain text narrative that identifies the resource in addition to the resource reference. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Summary | True | ||||||||||
| Comments | This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.encounter | |||||||||||
| Short | Context of the Composition | ||||||||||
| Definition | Describes the clinical encounter or type of care this documentation is associated with. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Reference(Encounter) | ||||||||||
| Summary | True | ||||||||||
| Requirements | Provides context for the composition and supports searching. | ||||||||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.date | |||||||||||
| Short | Composition editing time | ||||||||||
| Definition | The composition editing time, when the composition was last logically changed by the author. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | dateTime | ||||||||||
| Must Support | True | ||||||||||
| Summary | True | ||||||||||
| Requirements | dateTime is used for tracking, organizing versions and searching. Note that this is the time of authoring. When packaged in a document, Bundle.timestamp is the date of packaging. | ||||||||||
| Comments | The Last Modified Date on the composition may be after the date of the document was attested without being changed. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.author | |||||||||||
| Short | Who and/or what authored the IPS | ||||||||||
| Definition | Identifies who is responsible for the information in the composition, not necessarily who typed it in. | ||||||||||
| Cardinality | 1..* | ||||||||||
| Type | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||||||||||
| Must Support | True | ||||||||||
| Summary | True | ||||||||||
| Requirements | Identifies who is responsible for the content. | ||||||||||
| Comments | The distinction between the two types of IPS, "human-curated" or "software-assembled", is based on the authors recorded in this field: the author refers to humans (i.e. Practitioner, PractitionerRole, Patient, and/or RelatedPerson) if the IPS provenance is "human-curated", or devices (i.e. Device) if the IPS provenance is "software-assembled". In the case of a software-assembled IPS that is then verified by a human, the author would be the device that constructed the IPS document, but additional attesters would identity the humans who performed this check. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.title | |||||||||||
| Short | The title of this patient summary. This may include information like the patient name and time generated | ||||||||||
| Definition | Official human-readable label for the composition. This would typically include a label of "International Patient Summary" or any equivalent translation and other relevant document information | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | string | ||||||||||
| Must Support | True | ||||||||||
| Summary | True | ||||||||||
| Comments | For many compositions, the title is the same as the text or a display name of Composition.type (e.g. a "consultation" or "progress note"). Note that CDA does not make title mandatory, but there are no known cases where it is useful for title to be omitted, so it is mandatory here. Feedback on this requirement is welcome during the trial use period. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.confidentiality | |||||||||||
| Short | As defined by affinity domain | ||||||||||
| Definition | The code specifying the level of confidentiality of the Composition. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | code | ||||||||||
| Binding | Codes specifying the level of confidentiality of the composition. | ||||||||||
| Summary | True | ||||||||||
| Comments | The exact use of this element, and enforcement and issues related to highly sensitive documents are out of scope for the base specification, and delegated to implementation profiles (see security section). This element is labeled as a modifier because highly confidential documents must not be treated as if they are not. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.attester | |||||||||||
| Short | Attests to accuracy of composition | ||||||||||
| Definition | A participant who has attested to the accuracy of the composition/document. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | BackboneElement | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Identifies responsibility for the accuracy of the composition content. | ||||||||||
| Comments | Only list each attester once. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.attester.id | |||||||||||
| Short | Unique id for inter-element referencing | ||||||||||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Mappings |
| ||||||||||
| Composition.attester.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.attester.modifierExtension | |||||||||||
| Short | Extensions that cannot be ignored even if unrecognized | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Modifier | True | ||||||||||
| Summary | True | ||||||||||
| Alias | extensions, user content, modifiers | ||||||||||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.attester.mode | |||||||||||
| Short | personal | professional | legal | official | ||||||||||
| Definition | The type of attestation the authenticator offers. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | code | ||||||||||
| Binding | The way in which a person authenticated a composition. | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Indicates the level of authority of the attestation. | ||||||||||
| Comments | Note that FHIR strings SHALL NOT exceed 1MB in size | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.attester.time | |||||||||||
| Short | When the composition was attested | ||||||||||
| Definition | When the composition was attested by the party. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | dateTime | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Identifies when the information in the composition was deemed accurate. (Things may have changed since then.). | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.attester.party | |||||||||||
| Short | Who attested the composition | ||||||||||
| Definition | Who attested the composition in the specified way. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Reference(Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Identifies who has taken on the responsibility for accuracy of the composition content. | ||||||||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.custodian | |||||||||||
| Short | Organization which maintains the composition | ||||||||||
| Definition | Identifies the organization or group who is responsible for ongoing maintenance of and access to the composition/document information. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Reference(Organization) | ||||||||||
| Must Support | True | ||||||||||
| Summary | True | ||||||||||
| Requirements | Identifies where to go to find the current version, where to report issues, etc. | ||||||||||
| Comments | This is useful when documents are derived from a composition - provides guidance for how to get the latest version of the document. This is optional because this is sometimes not known by the authoring system, and can be inferred by context. However, it is important that this information be known when working with a derived document, so providing a custodian is encouraged. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.relatesTo | |||||||||||
| Short | Relationships to other compositions/documents | ||||||||||
| Definition | Relationships that this composition has with other compositions or documents that already exist. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | BackboneElement | ||||||||||
| Comments | A document is a version specific composition. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.relatesTo.id | |||||||||||
| Short | Unique id for inter-element referencing | ||||||||||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Mappings |
| ||||||||||
| Composition.relatesTo.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.relatesTo.modifierExtension | |||||||||||
| Short | Extensions that cannot be ignored even if unrecognized | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Modifier | True | ||||||||||
| Summary | True | ||||||||||
| Alias | extensions, user content, modifiers | ||||||||||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.relatesTo.code | |||||||||||
| Short | replaces | transforms | signs | appends | ||||||||||
| Definition | The type of relationship that this composition has with anther composition or document. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | code | ||||||||||
| Binding | The type of relationship between documents. | ||||||||||
| Comments | If this document appends another document, then the document cannot be fully understood without also accessing the referenced document. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.relatesTo.target[x] | |||||||||||
| Short | Target of the relationship | ||||||||||
| Definition | The target composition/document of this relationship. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | Identifier | Reference(Composition | CompositionUvIps) | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.event | |||||||||||
| Short | The clinical service(s) being documented | ||||||||||
| Definition | The main activity being described by a IPS is the provision of healthcare over a period of time. In the CDA representation of the IPS this is shown by setting the value of serviceEvent/@classCode to “PCPR” (care provision) and indicating the duration over which care was provided in serviceEvent/effectiveTime. In the FHIR representation at least one event should be used to record this information. Additional data from outside this duration may also be included if it is relevant to care provided during that time range (e.g., reviewed during the stated time range). For example if the IPS is generated by a GP based on information recorded in his/her EHR-S, then the start value should represent the date when the treatment relationship between the patient and the GP started; and the end value the date of the latest care event. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | BackboneElement | ||||||||||
| Summary | True | ||||||||||
| Requirements | Provides context for the composition and creates a linkage between a resource describing an event and the composition created describing the event. | ||||||||||
| Comments | The event needs to be consistent with the type element, though can provide further information if desired. | ||||||||||
| Slicing | Unordered, Open, by code(Value) | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.event.id | |||||||||||
| Short | Unique id for inter-element referencing | ||||||||||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Mappings |
| ||||||||||
| Composition.event.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.event.modifierExtension | |||||||||||
| Short | Extensions that cannot be ignored even if unrecognized | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Modifier | True | ||||||||||
| Summary | True | ||||||||||
| Alias | extensions, user content, modifiers | ||||||||||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.event.code | |||||||||||
| Short | Code(s) that apply to the event being documented | ||||||||||
| Definition | This list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the typeCode, such as a "History and Physical Report" in which the procedure being documented is necessarily a "History and Physical" act. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | This list of codes represents the main clinical acts being documented. | ||||||||||
| Summary | True | ||||||||||
| Comments | An event can further specialize the act inherent in the typeCode, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more eventCodes are included, they SHALL NOT conflict with the values inherent in the classCode, practiceSettingCode or typeCode, as such a conflict would create an ambiguous situation. This short list of codes is provided to be used as key words for certain types of queries. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.event.period | |||||||||||
| Short | The period covered by the documentation | ||||||||||
| Definition | The period of time covered by the documentation. There is no assertion that the documentation is a complete representation for this period, only that it documents events during this time. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Period | ||||||||||
| Summary | True | ||||||||||
| Comments | A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.event.detail | |||||||||||
| Short | The event(s) being documented | ||||||||||
| Definition | The description and/or reference of the event(s) being documented. For example, this could be used to document such a colonoscopy or an appendectomy. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Resource) | ||||||||||
| Summary | True | ||||||||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.event:careProvisioningEvent | |||||||||||
| Short | The care provisioning being documented | ||||||||||
| Definition | The provision of healthcare over a period of time this IPS is documenting. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | BackboneElement | ||||||||||
| Must Support | True | ||||||||||
| Summary | True | ||||||||||
| Requirements | Provides context for the composition and creates a linkage between a resource describing an event and the composition created describing the event. | ||||||||||
| Comments | The event needs to be consistent with the type element, though can provide further information if desired. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.event:careProvisioningEvent.id | |||||||||||
| Short | Unique id for inter-element referencing | ||||||||||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Mappings |
| ||||||||||
| Composition.event:careProvisioningEvent.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.event:careProvisioningEvent.modifierExtension | |||||||||||
| Short | Extensions that cannot be ignored even if unrecognized | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Modifier | True | ||||||||||
| Summary | True | ||||||||||
| Alias | extensions, user content, modifiers | ||||||||||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.event:careProvisioningEvent.code | |||||||||||
| Short | Code(s) that apply to the event being documented | ||||||||||
| Definition | This list of codes represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the typeCode, such as a "History and Physical Report" in which the procedure being documented is necessarily a "History and Physical" act. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | This list of codes represents the main clinical acts being documented. | ||||||||||
| Must Support | True | ||||||||||
| Summary | True | ||||||||||
| Comments | An event can further specialize the act inherent in the typeCode, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more eventCodes are included, they SHALL NOT conflict with the values inherent in the classCode, practiceSettingCode or typeCode, as such a conflict would create an ambiguous situation. This short list of codes is provided to be used as key words for certain types of queries. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Pattern | {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/v3-ActClass",
"code": "PCPR"
}
]
} | ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.event:careProvisioningEvent.period | |||||||||||
| Short | The period covered by the documentation | ||||||||||
| Definition | The period of time covered by the documentation. There is no assertion that the documentation is a complete representation for this period, only that it documents events during this time. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Period | ||||||||||
| Must Support | True | ||||||||||
| Summary | True | ||||||||||
| Comments | A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.event:careProvisioningEvent.detail | |||||||||||
| Short | The event(s) being documented | ||||||||||
| Definition | The description and/or reference of the event(s) being documented. For example, this could be used to document such a colonoscopy or an appendectomy. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Resource) | ||||||||||
| Summary | True | ||||||||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section | |||||||||||
| Short | Sections composing the IPS | ||||||||||
| Definition | The root of the sections that make up the IPS composition. | ||||||||||
| Cardinality | 3..* | ||||||||||
| Type | BackboneElement | ||||||||||
| Must Support | True | ||||||||||
| Slicing | Unordered, Open, by code(Value) | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section.id | |||||||||||
| Short | Unique id for inter-element referencing | ||||||||||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Mappings |
| ||||||||||
| Composition.section.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section.extension:section-note | |||||||||||
| Short | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Definition | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section.modifierExtension | |||||||||||
| Short | Extensions that cannot be ignored even if unrecognized | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Modifier | True | ||||||||||
| Summary | True | ||||||||||
| Alias | extensions, user content, modifiers | ||||||||||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section.title | |||||||||||
| Short | Label for section (e.g. for ToC) | ||||||||||
| Definition | The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | string | ||||||||||
| Must Support | True | ||||||||||
| Alias | header, label, caption | ||||||||||
| Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. | ||||||||||
| Comments | The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section.code | |||||||||||
| Short | Classification of section (recommended) | ||||||||||
| Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | Classification of a section of a composition/document. | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Provides computable standardized labels to topics within the document. | ||||||||||
| Comments | The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section.author | |||||||||||
| Short | Who and/or what authored the section | ||||||||||
| Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||||||||||
| Requirements | Identifies who is responsible for the content. | ||||||||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section.focus | |||||||||||
| Short | Who/what the section is about, when it is not about the subject of composition | ||||||||||
| Definition | The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Reference(Resource) | ||||||||||
| Comments | Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section.text | |||||||||||
| Short | Text summary of the section, for human interpretation | ||||||||||
| Definition | A human-readable narrative that contains the attested content of the section, used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | Narrative | ||||||||||
| Must Support | True | ||||||||||
| Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section.mode | |||||||||||
| Short | working | snapshot | changes | ||||||||||
| Definition | How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | code | ||||||||||
| Binding | The processing mode that applies to this section. | ||||||||||
| Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. | ||||||||||
| Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section.orderedBy | |||||||||||
| Short | Order of section entries | ||||||||||
| Definition | Specifies the order applied to the items in the section entries. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | What order applies to the items in the entry. | ||||||||||
| Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. | ||||||||||
| Comments | Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section.entry | |||||||||||
| Short | A reference to data that supports this section | ||||||||||
| Definition | A reference to the actual resource from which the narrative in the section is derived. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Resource) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section.emptyReason | |||||||||||
| Short | Why the section is empty | ||||||||||
| Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | If a section is empty, why it is empty. | ||||||||||
| Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists. | ||||||||||
| Comments | The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section.section | |||||||||||
| Short | Nested Section | ||||||||||
| Definition | A nested sub-section within this section. | ||||||||||
| Cardinality | 0..0 | ||||||||||
| Type | see (section) | ||||||||||
| Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cmp-1 | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionProblems | |||||||||||
| Short | IPS Problems Section | ||||||||||
| Definition | The IPS problem section lists and describes clinical problems or conditions currently being monitored for the patient. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | BackboneElement | ||||||||||
| Must Support | True | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionProblems.id | |||||||||||
| Short | Unique id for inter-element referencing | ||||||||||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionProblems.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionProblems.extension:section-note | |||||||||||
| Short | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Definition | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionProblems.modifierExtension | |||||||||||
| Short | Extensions that cannot be ignored even if unrecognized | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Modifier | True | ||||||||||
| Summary | True | ||||||||||
| Alias | extensions, user content, modifiers | ||||||||||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionProblems.title | |||||||||||
| Short | Label for section (e.g. for ToC) | ||||||||||
| Definition | The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | string | ||||||||||
| Must Support | True | ||||||||||
| Alias | header, label, caption | ||||||||||
| Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. | ||||||||||
| Comments | The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionProblems.code | |||||||||||
| Short | Classification of section (recommended) | ||||||||||
| Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | Classification of a section of a composition/document. | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Provides computable standardized labels to topics within the document. | ||||||||||
| Comments | The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Pattern | {
"coding": [
{
"system": "http://loinc.org",
"code": "11450-4"
}
]
} | ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionProblems.author | |||||||||||
| Short | Who and/or what authored the section | ||||||||||
| Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||||||||||
| Requirements | Identifies who is responsible for the content. | ||||||||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionProblems.focus | |||||||||||
| Short | Who/what the section is about, when it is not about the subject of composition | ||||||||||
| Definition | The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Reference(Resource) | ||||||||||
| Comments | Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionProblems.text | |||||||||||
| Short | Text summary of the section, for human interpretation | ||||||||||
| Definition | A human-readable narrative that contains the attested content of the section, used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | Narrative | ||||||||||
| Must Support | True | ||||||||||
| Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionProblems.mode | |||||||||||
| Short | working | snapshot | changes | ||||||||||
| Definition | How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | code | ||||||||||
| Binding | The processing mode that applies to this section. | ||||||||||
| Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. | ||||||||||
| Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionProblems.orderedBy | |||||||||||
| Short | Order of section entries | ||||||||||
| Definition | Specifies the order applied to the items in the section entries. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | What order applies to the items in the entry. | ||||||||||
| Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. | ||||||||||
| Comments | Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionProblems.entry | |||||||||||
| Short | Clinical problems or conditions currently being monitored for the patient. | ||||||||||
| Definition | It lists and describes clinical problems or conditions currently being monitored for the patient. This entry shall be used to document that no information about problems is available, or that no relevant problems are known. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Condition | DocumentReference) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Slicing | Unordered, Open, by resolve()(Profile) | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionProblems.entry:problem | |||||||||||
| Short | A reference to data that supports this section | ||||||||||
| Definition | A reference to the actual resource from which the narrative in the section is derived. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(ConditionUvIps) | ||||||||||
| Must Support | True | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionProblems.emptyReason | |||||||||||
| Short | Why the section is empty | ||||||||||
| Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | If a section is empty, why it is empty. | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists. | ||||||||||
| Comments | The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionProblems.section | |||||||||||
| Short | Nested Section | ||||||||||
| Definition | A nested sub-section within this section. | ||||||||||
| Cardinality | 0..0 | ||||||||||
| Type | see (section) | ||||||||||
| Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cmp-1 | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAllergies | |||||||||||
| Short | IPS Allergies and Intolerances Section | ||||||||||
| Definition | This section documents the relevant allergies or intolerances for that patient, describing the kind of reaction (e.g. rash, anaphylaxis,..); preferably the agents that cause it; and optionally the criticality and the certainty of the allergy. At a minimum, it should list currently active and any relevant historical allergies and adverse reactions. If no information about allergies is available, or if no allergies are known this should be clearly documented in the section. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | BackboneElement | ||||||||||
| Must Support | True | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionAllergies.id | |||||||||||
| Short | Unique id for inter-element referencing | ||||||||||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAllergies.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAllergies.extension:section-note | |||||||||||
| Short | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Definition | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAllergies.modifierExtension | |||||||||||
| Short | Extensions that cannot be ignored even if unrecognized | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Modifier | True | ||||||||||
| Summary | True | ||||||||||
| Alias | extensions, user content, modifiers | ||||||||||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAllergies.title | |||||||||||
| Short | Label for section (e.g. for ToC) | ||||||||||
| Definition | The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | string | ||||||||||
| Must Support | True | ||||||||||
| Alias | header, label, caption | ||||||||||
| Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. | ||||||||||
| Comments | The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionAllergies.code | |||||||||||
| Short | Classification of section (recommended) | ||||||||||
| Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | Classification of a section of a composition/document. | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Provides computable standardized labels to topics within the document. | ||||||||||
| Comments | The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Pattern | {
"coding": [
{
"system": "http://loinc.org",
"code": "48765-2"
}
]
} | ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionAllergies.author | |||||||||||
| Short | Who and/or what authored the section | ||||||||||
| Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||||||||||
| Requirements | Identifies who is responsible for the content. | ||||||||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAllergies.focus | |||||||||||
| Short | Who/what the section is about, when it is not about the subject of composition | ||||||||||
| Definition | The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Reference(Resource) | ||||||||||
| Comments | Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAllergies.text | |||||||||||
| Short | Text summary of the section, for human interpretation | ||||||||||
| Definition | A human-readable narrative that contains the attested content of the section, used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | Narrative | ||||||||||
| Must Support | True | ||||||||||
| Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionAllergies.mode | |||||||||||
| Short | working | snapshot | changes | ||||||||||
| Definition | How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | code | ||||||||||
| Binding | The processing mode that applies to this section. | ||||||||||
| Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. | ||||||||||
| Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAllergies.orderedBy | |||||||||||
| Short | Order of section entries | ||||||||||
| Definition | Specifies the order applied to the items in the section entries. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | What order applies to the items in the entry. | ||||||||||
| Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. | ||||||||||
| Comments | Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAllergies.entry | |||||||||||
| Short | Relevant allergies or intolerances for that patient. | ||||||||||
| Definition | It lists the relevant allergies or intolerances for that patient, describing the kind of reaction (e.g. rash, anaphylaxis,..); preferably the agents that cause it; and optionally the criticality and the certainty of the allergy. At a minimum, it should list currently active and any relevant historical allergies and adverse reactions. This entry shall be used to document that no information about allergies is available, or that no allergies are known . | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(AllergyIntolerance | DocumentReference) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Slicing | Unordered, Open, by resolve()(Profile) | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAllergies.entry:allergyOrIntolerance | |||||||||||
| Short | A reference to data that supports this section | ||||||||||
| Definition | A reference to the actual resource from which the narrative in the section is derived. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(AllergyIntoleranceUvIps) | ||||||||||
| Must Support | True | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionAllergies.emptyReason | |||||||||||
| Short | Why the section is empty | ||||||||||
| Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | If a section is empty, why it is empty. | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists. | ||||||||||
| Comments | The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionAllergies.section | |||||||||||
| Short | Nested Section | ||||||||||
| Definition | A nested sub-section within this section. | ||||||||||
| Cardinality | 0..0 | ||||||||||
| Type | see (section) | ||||||||||
| Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cmp-1 | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionMedications | |||||||||||
| Short | IPS Medication Summary Section | ||||||||||
| Definition | The medication summary section contains a description of the patient's medications relevant for the scope of the patient summary. The actual content could depend on the jurisdiction, it could report:
In those cases medications are documented in the Patient Summary as medication statements or medication requests. This section requires either an entry indicating the subject is known not to be on any relevant medication; either an entry indicating that no information is available about medications; or entries summarizing the subject's relevant medications. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | BackboneElement | ||||||||||
| Must Support | True | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionMedications.id | |||||||||||
| Short | Unique id for inter-element referencing | ||||||||||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionMedications.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionMedications.extension:section-note | |||||||||||
| Short | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Definition | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionMedications.modifierExtension | |||||||||||
| Short | Extensions that cannot be ignored even if unrecognized | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Modifier | True | ||||||||||
| Summary | True | ||||||||||
| Alias | extensions, user content, modifiers | ||||||||||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionMedications.title | |||||||||||
| Short | Label for section (e.g. for ToC) | ||||||||||
| Definition | The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | string | ||||||||||
| Must Support | True | ||||||||||
| Alias | header, label, caption | ||||||||||
| Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. | ||||||||||
| Comments | The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionMedications.code | |||||||||||
| Short | Classification of section (recommended) | ||||||||||
| Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | Classification of a section of a composition/document. | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Provides computable standardized labels to topics within the document. | ||||||||||
| Comments | The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Pattern | {
"coding": [
{
"system": "http://loinc.org",
"code": "10160-0"
}
]
} | ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionMedications.author | |||||||||||
| Short | Who and/or what authored the section | ||||||||||
| Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||||||||||
| Requirements | Identifies who is responsible for the content. | ||||||||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionMedications.focus | |||||||||||
| Short | Who/what the section is about, when it is not about the subject of composition | ||||||||||
| Definition | The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Reference(Resource) | ||||||||||
| Comments | Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionMedications.text | |||||||||||
| Short | Text summary of the section, for human interpretation | ||||||||||
| Definition | A human-readable narrative that contains the attested content of the section, used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | Narrative | ||||||||||
| Must Support | True | ||||||||||
| Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionMedications.mode | |||||||||||
| Short | working | snapshot | changes | ||||||||||
| Definition | How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | code | ||||||||||
| Binding | The processing mode that applies to this section. | ||||||||||
| Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. | ||||||||||
| Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionMedications.orderedBy | |||||||||||
| Short | Order of section entries | ||||||||||
| Definition | Specifies the order applied to the items in the section entries. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | What order applies to the items in the entry. | ||||||||||
| Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. | ||||||||||
| Comments | Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionMedications.entry | |||||||||||
| Short | Medications relevant for the scope of the patient summary | ||||||||||
| Definition | This list the medications relevant for the scope of the patient summary or it is used to indicate that the subject is known not to be on any relevant medication; either that no information is available about medications. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(DocumentReference | MedicationAdministration | MedicationDispense | MedicationRequest | MedicationStatement) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Slicing | Unordered, Open, by resolve()(Profile) | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionMedications.entry:medicationStatementOrRequest | |||||||||||
| Short | A reference to data that supports this section | ||||||||||
| Definition | A reference to the actual resource from which the narrative in the section is derived. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(MedicationRequestIPS | MedicationStatementIPS) | ||||||||||
| Must Support | True | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionMedications.emptyReason | |||||||||||
| Short | Why the section is empty | ||||||||||
| Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | If a section is empty, why it is empty. | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists. | ||||||||||
| Comments | The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionMedications.section | |||||||||||
| Short | Nested Section | ||||||||||
| Definition | A nested sub-section within this section. | ||||||||||
| Cardinality | 0..0 | ||||||||||
| Type | see (section) | ||||||||||
| Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cmp-1 | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionImmunizations | |||||||||||
| Short | IPS Immunizations Section | ||||||||||
| Definition | The Immunizations Section defines a patient's current immunization status and pertinent immunization history. The primary use case for the Immunization Section is to enable communication of a patient's immunization status. The section includes the current immunization status, and may contain the entire immunization history that is relevant to the period of time being summarized. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | BackboneElement | ||||||||||
| Must Support | True | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionImmunizations.id | |||||||||||
| Short | Unique id for inter-element referencing | ||||||||||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionImmunizations.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionImmunizations.extension:section-note | |||||||||||
| Short | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Definition | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionImmunizations.modifierExtension | |||||||||||
| Short | Extensions that cannot be ignored even if unrecognized | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Modifier | True | ||||||||||
| Summary | True | ||||||||||
| Alias | extensions, user content, modifiers | ||||||||||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionImmunizations.title | |||||||||||
| Short | Label for section (e.g. for ToC) | ||||||||||
| Definition | The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | string | ||||||||||
| Must Support | True | ||||||||||
| Alias | header, label, caption | ||||||||||
| Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. | ||||||||||
| Comments | The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionImmunizations.code | |||||||||||
| Short | Classification of section (recommended) | ||||||||||
| Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | Classification of a section of a composition/document. | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Provides computable standardized labels to topics within the document. | ||||||||||
| Comments | The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Pattern | {
"coding": [
{
"system": "http://loinc.org",
"code": "11369-6"
}
]
} | ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionImmunizations.author | |||||||||||
| Short | Who and/or what authored the section | ||||||||||
| Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||||||||||
| Requirements | Identifies who is responsible for the content. | ||||||||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionImmunizations.focus | |||||||||||
| Short | Who/what the section is about, when it is not about the subject of composition | ||||||||||
| Definition | The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Reference(Resource) | ||||||||||
| Comments | Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionImmunizations.text | |||||||||||
| Short | Text summary of the section, for human interpretation | ||||||||||
| Definition | A human-readable narrative that contains the attested content of the section, used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | Narrative | ||||||||||
| Must Support | True | ||||||||||
| Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionImmunizations.mode | |||||||||||
| Short | working | snapshot | changes | ||||||||||
| Definition | How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | code | ||||||||||
| Binding | The processing mode that applies to this section. | ||||||||||
| Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. | ||||||||||
| Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionImmunizations.orderedBy | |||||||||||
| Short | Order of section entries | ||||||||||
| Definition | Specifies the order applied to the items in the section entries. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | What order applies to the items in the entry. | ||||||||||
| Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. | ||||||||||
| Comments | Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionImmunizations.entry | |||||||||||
| Short | Patient's immunization status and pertinent history. | ||||||||||
| Definition | It defines the patient's current immunization status and pertinent immunization history. The primary use case for the Immunization Section is to enable communication of a patient's immunization status. It may contain the entire immunization history that is relevant to the period of time being summarized. This entry shall be used to document that no information about immunizations is available, or that no immunizations are known. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(DocumentReference | Immunization) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Slicing | Unordered, Open, by resolve()(Profile) | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionImmunizations.entry:immunization | |||||||||||
| Short | A reference to data that supports this section | ||||||||||
| Definition | A reference to the actual resource from which the narrative in the section is derived. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(ImmunizationUvIps) | ||||||||||
| Must Support | True | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionImmunizations.emptyReason | |||||||||||
| Short | Why the section is empty | ||||||||||
| Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | If a section is empty, why it is empty. | ||||||||||
| Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists. | ||||||||||
| Comments | The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionImmunizations.section | |||||||||||
| Short | Nested Section | ||||||||||
| Definition | A nested sub-section within this section. | ||||||||||
| Cardinality | 0..0 | ||||||||||
| Type | see (section) | ||||||||||
| Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cmp-1 | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionResults | |||||||||||
| Short | IPS Results Section | ||||||||||
| Definition | This section assembles relevant observation results collected on the patient or produced on in-vitro biologic specimens collected from the patient. Some of these results may be laboratory results, others may be anatomic pathology results, others, radiology results, and others, clinical results. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | BackboneElement | ||||||||||
| Must Support | True | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionResults.id | |||||||||||
| Short | Unique id for inter-element referencing | ||||||||||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionResults.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionResults.extension:section-note | |||||||||||
| Short | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Definition | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionResults.modifierExtension | |||||||||||
| Short | Extensions that cannot be ignored even if unrecognized | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Modifier | True | ||||||||||
| Summary | True | ||||||||||
| Alias | extensions, user content, modifiers | ||||||||||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionResults.title | |||||||||||
| Short | Label for section (e.g. for ToC) | ||||||||||
| Definition | The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | string | ||||||||||
| Must Support | True | ||||||||||
| Alias | header, label, caption | ||||||||||
| Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. | ||||||||||
| Comments | The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionResults.code | |||||||||||
| Short | Classification of section (recommended) | ||||||||||
| Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | Classification of a section of a composition/document. | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Provides computable standardized labels to topics within the document. | ||||||||||
| Comments | The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Pattern | {
"coding": [
{
"system": "http://loinc.org",
"code": "30954-2"
}
]
} | ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionResults.author | |||||||||||
| Short | Who and/or what authored the section | ||||||||||
| Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||||||||||
| Requirements | Identifies who is responsible for the content. | ||||||||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionResults.focus | |||||||||||
| Short | Who/what the section is about, when it is not about the subject of composition | ||||||||||
| Definition | The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Reference(Resource) | ||||||||||
| Comments | Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionResults.text | |||||||||||
| Short | Text summary of the section, for human interpretation | ||||||||||
| Definition | A human-readable narrative that contains the attested content of the section, used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | Narrative | ||||||||||
| Must Support | True | ||||||||||
| Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionResults.mode | |||||||||||
| Short | working | snapshot | changes | ||||||||||
| Definition | How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | code | ||||||||||
| Binding | The processing mode that applies to this section. | ||||||||||
| Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. | ||||||||||
| Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionResults.orderedBy | |||||||||||
| Short | Order of section entries | ||||||||||
| Definition | Specifies the order applied to the items in the section entries. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | What order applies to the items in the entry. | ||||||||||
| Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. | ||||||||||
| Comments | Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionResults.entry | |||||||||||
| Short | Relevant observation results collected on the patient or produced on in-vitro biologic specimens collected from the patient. | ||||||||||
| Definition | Relevant observation results collected on the patient or produced on in-vitro biologic specimens collected from the patient. Some of these results may be laboratory results, others may be anatomic pathology results, others, radiology results, and others, clinical results. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(DiagnosticReport | DocumentReference | Observation) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Slicing | Unordered, Open, by resolve()(Type), resolve()(Profile) | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionResults.entry:results-observation-laboratory-pathology | |||||||||||
| Short | A reference to data that supports this section | ||||||||||
| Definition | A reference to the actual resource from which the narrative in the section is derived. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(ObservationResultsLaboratoryPathologyUvIps) | ||||||||||
| Must Support | True | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionResults.entry:results-observation-radiology | |||||||||||
| Short | A reference to data that supports this section | ||||||||||
| Definition | A reference to the actual resource from which the narrative in the section is derived. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(ObservationResultsRadiologyUvIps) | ||||||||||
| Must Support | True | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionResults.entry:results-diagnosticReport | |||||||||||
| Short | A reference to data that supports this section | ||||||||||
| Definition | A reference to the actual resource from which the narrative in the section is derived. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(DiagnosticReportUvIps) | ||||||||||
| Must Support | True | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionResults.emptyReason | |||||||||||
| Short | Why the section is empty | ||||||||||
| Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | If a section is empty, why it is empty. | ||||||||||
| Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists. | ||||||||||
| Comments | The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionResults.section | |||||||||||
| Short | Nested Section | ||||||||||
| Definition | A nested sub-section within this section. | ||||||||||
| Cardinality | 0..0 | ||||||||||
| Type | see (section) | ||||||||||
| Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cmp-1 | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionProceduresHx | |||||||||||
| Short | IPS History of Procedures Section | ||||||||||
| Definition | The History of Procedures Section contains a description of the patient past procedures that are pertinent to the scope of this document. Procedures may refer for example to:
| ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | BackboneElement | ||||||||||
| Must Support | True | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionProceduresHx.id | |||||||||||
| Short | Unique id for inter-element referencing | ||||||||||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionProceduresHx.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionProceduresHx.extension:section-note | |||||||||||
| Short | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Definition | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionProceduresHx.modifierExtension | |||||||||||
| Short | Extensions that cannot be ignored even if unrecognized | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Modifier | True | ||||||||||
| Summary | True | ||||||||||
| Alias | extensions, user content, modifiers | ||||||||||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionProceduresHx.title | |||||||||||
| Short | Label for section (e.g. for ToC) | ||||||||||
| Definition | The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | string | ||||||||||
| Must Support | True | ||||||||||
| Alias | header, label, caption | ||||||||||
| Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. | ||||||||||
| Comments | The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionProceduresHx.code | |||||||||||
| Short | Classification of section (recommended) | ||||||||||
| Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | Classification of a section of a composition/document. | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Provides computable standardized labels to topics within the document. | ||||||||||
| Comments | The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Pattern | {
"coding": [
{
"system": "http://loinc.org",
"code": "47519-4"
}
]
} | ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionProceduresHx.author | |||||||||||
| Short | Who and/or what authored the section | ||||||||||
| Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||||||||||
| Requirements | Identifies who is responsible for the content. | ||||||||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionProceduresHx.focus | |||||||||||
| Short | Who/what the section is about, when it is not about the subject of composition | ||||||||||
| Definition | The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Reference(Resource) | ||||||||||
| Comments | Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionProceduresHx.text | |||||||||||
| Short | Text summary of the section, for human interpretation | ||||||||||
| Definition | A human-readable narrative that contains the attested content of the section, used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | Narrative | ||||||||||
| Must Support | True | ||||||||||
| Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionProceduresHx.mode | |||||||||||
| Short | working | snapshot | changes | ||||||||||
| Definition | How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | code | ||||||||||
| Binding | The processing mode that applies to this section. | ||||||||||
| Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. | ||||||||||
| Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionProceduresHx.orderedBy | |||||||||||
| Short | Order of section entries | ||||||||||
| Definition | Specifies the order applied to the items in the section entries. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | What order applies to the items in the entry. | ||||||||||
| Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. | ||||||||||
| Comments | Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionProceduresHx.entry | |||||||||||
| Short | Patient past procedures pertinent to the scope of this document. | ||||||||||
| Definition | It lists the patient past procedures that are pertinent to the scope of this document. Procedures may refer for example to:
| ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(DocumentReference | Procedure) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Slicing | Unordered, Open, by resolve()(Profile) | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionProceduresHx.entry:procedure | |||||||||||
| Short | A reference to data that supports this section | ||||||||||
| Definition | A reference to the actual resource from which the narrative in the section is derived. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(ProcedureUvIps) | ||||||||||
| Must Support | True | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionProceduresHx.emptyReason | |||||||||||
| Short | Why the section is empty | ||||||||||
| Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | If a section is empty, why it is empty. | ||||||||||
| Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists. | ||||||||||
| Comments | The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionProceduresHx.section | |||||||||||
| Short | Nested Section | ||||||||||
| Definition | A nested sub-section within this section. | ||||||||||
| Cardinality | 0..0 | ||||||||||
| Type | see (section) | ||||||||||
| Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cmp-1 | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionMedicalDevices | |||||||||||
| Short | IPS Medical Devices Section | ||||||||||
| Definition | The medical devices section contains narrative text and coded entries describing the patient history of medical device use. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | BackboneElement | ||||||||||
| Must Support | True | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionMedicalDevices.id | |||||||||||
| Short | Unique id for inter-element referencing | ||||||||||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionMedicalDevices.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionMedicalDevices.extension:section-note | |||||||||||
| Short | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Definition | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionMedicalDevices.modifierExtension | |||||||||||
| Short | Extensions that cannot be ignored even if unrecognized | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Modifier | True | ||||||||||
| Summary | True | ||||||||||
| Alias | extensions, user content, modifiers | ||||||||||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionMedicalDevices.title | |||||||||||
| Short | Label for section (e.g. for ToC) | ||||||||||
| Definition | The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | string | ||||||||||
| Must Support | True | ||||||||||
| Alias | header, label, caption | ||||||||||
| Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. | ||||||||||
| Comments | The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionMedicalDevices.code | |||||||||||
| Short | Classification of section (recommended) | ||||||||||
| Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | Classification of a section of a composition/document. | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Provides computable standardized labels to topics within the document. | ||||||||||
| Comments | The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Pattern | {
"coding": [
{
"system": "http://loinc.org",
"code": "46264-8"
}
]
} | ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionMedicalDevices.author | |||||||||||
| Short | Who and/or what authored the section | ||||||||||
| Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||||||||||
| Requirements | Identifies who is responsible for the content. | ||||||||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionMedicalDevices.focus | |||||||||||
| Short | Who/what the section is about, when it is not about the subject of composition | ||||||||||
| Definition | The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Reference(Resource) | ||||||||||
| Comments | Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionMedicalDevices.text | |||||||||||
| Short | Text summary of the section, for human interpretation | ||||||||||
| Definition | A human-readable narrative that contains the attested content of the section, used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | Narrative | ||||||||||
| Must Support | True | ||||||||||
| Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionMedicalDevices.mode | |||||||||||
| Short | working | snapshot | changes | ||||||||||
| Definition | How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | code | ||||||||||
| Binding | The processing mode that applies to this section. | ||||||||||
| Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. | ||||||||||
| Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionMedicalDevices.orderedBy | |||||||||||
| Short | Order of section entries | ||||||||||
| Definition | Specifies the order applied to the items in the section entries. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | What order applies to the items in the entry. | ||||||||||
| Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. | ||||||||||
| Comments | Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionMedicalDevices.entry | |||||||||||
| Short | Patient history of medical device use. | ||||||||||
| Definition | It describes the patient history of medical device use. This entry shall be used to document that no information about medical device use is available, or that no relevant medical device use is known. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(DeviceUseStatement | DocumentReference) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Slicing | Unordered, Open, by resolve()(Profile) | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionMedicalDevices.entry:deviceStatement | |||||||||||
| Short | A reference to data that supports this section | ||||||||||
| Definition | A reference to the actual resource from which the narrative in the section is derived. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(DeviceUseStatementUvIps) | ||||||||||
| Must Support | True | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionMedicalDevices.emptyReason | |||||||||||
| Short | Why the section is empty | ||||||||||
| Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | If a section is empty, why it is empty. | ||||||||||
| Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists. | ||||||||||
| Comments | The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionMedicalDevices.section | |||||||||||
| Short | Nested Section | ||||||||||
| Definition | A nested sub-section within this section. | ||||||||||
| Cardinality | 0..0 | ||||||||||
| Type | see (section) | ||||||||||
| Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cmp-1 | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAdvanceDirectives | |||||||||||
| Short | IPS Advance Directives Section | ||||||||||
| Definition | The advance directives section contains a narrative description of patient's advance directive. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | BackboneElement | ||||||||||
| Must Support | True | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionAdvanceDirectives.id | |||||||||||
| Short | Unique id for inter-element referencing | ||||||||||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAdvanceDirectives.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAdvanceDirectives.extension:section-note | |||||||||||
| Short | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Definition | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAdvanceDirectives.modifierExtension | |||||||||||
| Short | Extensions that cannot be ignored even if unrecognized | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Modifier | True | ||||||||||
| Summary | True | ||||||||||
| Alias | extensions, user content, modifiers | ||||||||||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAdvanceDirectives.title | |||||||||||
| Short | Label for section (e.g. for ToC) | ||||||||||
| Definition | The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | string | ||||||||||
| Must Support | True | ||||||||||
| Alias | header, label, caption | ||||||||||
| Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. | ||||||||||
| Comments | The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionAdvanceDirectives.code | |||||||||||
| Short | Classification of section (recommended) | ||||||||||
| Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | Classification of a section of a composition/document. | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Provides computable standardized labels to topics within the document. | ||||||||||
| Comments | The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Pattern | {
"coding": [
{
"system": "http://loinc.org",
"code": "42348-3"
}
]
} | ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionAdvanceDirectives.author | |||||||||||
| Short | Who and/or what authored the section | ||||||||||
| Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||||||||||
| Requirements | Identifies who is responsible for the content. | ||||||||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAdvanceDirectives.focus | |||||||||||
| Short | Who/what the section is about, when it is not about the subject of composition | ||||||||||
| Definition | The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Reference(Resource) | ||||||||||
| Comments | Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAdvanceDirectives.text | |||||||||||
| Short | Text summary of the section, for human interpretation | ||||||||||
| Definition | A human-readable narrative that contains the attested content of the section, used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | Narrative | ||||||||||
| Must Support | True | ||||||||||
| Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionAdvanceDirectives.mode | |||||||||||
| Short | working | snapshot | changes | ||||||||||
| Definition | How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | code | ||||||||||
| Binding | The processing mode that applies to this section. | ||||||||||
| Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. | ||||||||||
| Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAdvanceDirectives.orderedBy | |||||||||||
| Short | Order of section entries | ||||||||||
| Definition | Specifies the order applied to the items in the section entries. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | What order applies to the items in the entry. | ||||||||||
| Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. | ||||||||||
| Comments | Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAdvanceDirectives.entry | |||||||||||
| Short | Narrative description of the patient's advance directive. | ||||||||||
| Definition | Contains a narrative description or a Consent entry with information about the patient's advance directive. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Consent | DocumentReference) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Slicing | Unordered, Open, by resolve()(Profile) | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAdvanceDirectives.entry:advanceDirectivesConsent | |||||||||||
| Short | A reference to data that supports this section | ||||||||||
| Definition | A reference to the actual resource from which the narrative in the section is derived. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Consent) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAdvanceDirectives.emptyReason | |||||||||||
| Short | Why the section is empty | ||||||||||
| Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | If a section is empty, why it is empty. | ||||||||||
| Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists. | ||||||||||
| Comments | The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAdvanceDirectives.section | |||||||||||
| Short | Nested Section | ||||||||||
| Definition | A nested sub-section within this section. | ||||||||||
| Cardinality | 0..0 | ||||||||||
| Type | see (section) | ||||||||||
| Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cmp-1 | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAlerts | |||||||||||
| Short | IPS Alerts Section | ||||||||||
| Definition | The alerts section flags potential concerns and/or dangers to/from the patient and may also include obstacles to care. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | BackboneElement | ||||||||||
| Must Support | True | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionAlerts.id | |||||||||||
| Short | Unique id for inter-element referencing | ||||||||||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAlerts.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAlerts.extension:section-note | |||||||||||
| Short | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Definition | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAlerts.modifierExtension | |||||||||||
| Short | Extensions that cannot be ignored even if unrecognized | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Modifier | True | ||||||||||
| Summary | True | ||||||||||
| Alias | extensions, user content, modifiers | ||||||||||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAlerts.title | |||||||||||
| Short | Label for section (e.g. for ToC) | ||||||||||
| Definition | The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | string | ||||||||||
| Must Support | True | ||||||||||
| Alias | header, label, caption | ||||||||||
| Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. | ||||||||||
| Comments | The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionAlerts.code | |||||||||||
| Short | Classification of section (recommended) | ||||||||||
| Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | Classification of a section of a composition/document. | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Provides computable standardized labels to topics within the document. | ||||||||||
| Comments | The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Pattern | {
"coding": [
{
"system": "http://loinc.org",
"code": "104605-1"
}
]
} | ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionAlerts.author | |||||||||||
| Short | Who and/or what authored the section | ||||||||||
| Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||||||||||
| Requirements | Identifies who is responsible for the content. | ||||||||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAlerts.focus | |||||||||||
| Short | Who/what the section is about, when it is not about the subject of composition | ||||||||||
| Definition | The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Reference(Resource) | ||||||||||
| Comments | Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAlerts.text | |||||||||||
| Short | Text summary of the section, for human interpretation | ||||||||||
| Definition | A human-readable narrative that contains the attested content of the section, used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | Narrative | ||||||||||
| Must Support | True | ||||||||||
| Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionAlerts.mode | |||||||||||
| Short | working | snapshot | changes | ||||||||||
| Definition | How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | code | ||||||||||
| Binding | The processing mode that applies to this section. | ||||||||||
| Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. | ||||||||||
| Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAlerts.orderedBy | |||||||||||
| Short | Order of section entries | ||||||||||
| Definition | Specifies the order applied to the items in the section entries. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | What order applies to the items in the entry. | ||||||||||
| Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. | ||||||||||
| Comments | Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAlerts.entry | |||||||||||
| Short | Alert information. | ||||||||||
| Definition | Contains alert information to be communicated. May optionally reference other resources in IPS. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(DocumentReference | Flag) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Slicing | Unordered, Open, by resolve()(Profile) | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAlerts.entry:alertsFlag | |||||||||||
| Short | A reference to data that supports this section | ||||||||||
| Definition | A reference to the actual resource from which the narrative in the section is derived. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(FlagAlertUvIps) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAlerts.emptyReason | |||||||||||
| Short | Why the section is empty | ||||||||||
| Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | If a section is empty, why it is empty. | ||||||||||
| Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists. | ||||||||||
| Comments | The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionAlerts.section | |||||||||||
| Short | Nested Section | ||||||||||
| Definition | A nested sub-section within this section. | ||||||||||
| Cardinality | 0..0 | ||||||||||
| Type | see (section) | ||||||||||
| Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cmp-1 | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionFunctionalStatus | |||||||||||
| Short | IPS Functional Status | ||||||||||
| Definition | The functional status section shall contain a narrative description of capability of the patient to perform acts of daily living, including possible needs of the patient to be continuously assessed by third parties. The invalidity status may in fact influence decisions about how to administer treatments. Profiles to express disabilities and functional assessments will be specified by future versions of this guide. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | BackboneElement | ||||||||||
| Must Support | True | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionFunctionalStatus.id | |||||||||||
| Short | Unique id for inter-element referencing | ||||||||||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionFunctionalStatus.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionFunctionalStatus.extension:section-note | |||||||||||
| Short | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Definition | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionFunctionalStatus.modifierExtension | |||||||||||
| Short | Extensions that cannot be ignored even if unrecognized | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Modifier | True | ||||||||||
| Summary | True | ||||||||||
| Alias | extensions, user content, modifiers | ||||||||||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionFunctionalStatus.title | |||||||||||
| Short | Label for section (e.g. for ToC) | ||||||||||
| Definition | The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | string | ||||||||||
| Must Support | True | ||||||||||
| Alias | header, label, caption | ||||||||||
| Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. | ||||||||||
| Comments | The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionFunctionalStatus.code | |||||||||||
| Short | Classification of section (recommended) | ||||||||||
| Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | Classification of a section of a composition/document. | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Provides computable standardized labels to topics within the document. | ||||||||||
| Comments | The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Pattern | {
"coding": [
{
"system": "http://loinc.org",
"code": "47420-5"
}
]
} | ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionFunctionalStatus.author | |||||||||||
| Short | Who and/or what authored the section | ||||||||||
| Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||||||||||
| Requirements | Identifies who is responsible for the content. | ||||||||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionFunctionalStatus.focus | |||||||||||
| Short | Who/what the section is about, when it is not about the subject of composition | ||||||||||
| Definition | The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Reference(Resource) | ||||||||||
| Comments | Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionFunctionalStatus.text | |||||||||||
| Short | Text summary of the section, for human interpretation | ||||||||||
| Definition | A human-readable narrative that contains the attested content of the section, used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | Narrative | ||||||||||
| Must Support | True | ||||||||||
| Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionFunctionalStatus.mode | |||||||||||
| Short | working | snapshot | changes | ||||||||||
| Definition | How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | code | ||||||||||
| Binding | The processing mode that applies to this section. | ||||||||||
| Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. | ||||||||||
| Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionFunctionalStatus.orderedBy | |||||||||||
| Short | Order of section entries | ||||||||||
| Definition | Specifies the order applied to the items in the section entries. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | What order applies to the items in the entry. | ||||||||||
| Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. | ||||||||||
| Comments | Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionFunctionalStatus.entry | |||||||||||
| Short | Optional entry used to represent disabilities and functional assessments | ||||||||||
| Definition | It describes capabilities of the patient to perform acts of daily living, including possible needs of the patient to be continuously assessed by third parties. The invalidity status may in fact influence decisions about how to administer treatments. Profiles to express disabilities and functional assessments will be specified by future versions of this guide. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(ClinicalImpression | Condition | DocumentReference) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Slicing | Unordered, Open, by resolve()(Profile) | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionFunctionalStatus.entry:disability | |||||||||||
| Short | A reference to data that supports this section | ||||||||||
| Definition | A reference to the actual resource from which the narrative in the section is derived. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(ConditionUvIps) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionFunctionalStatus.entry:functionalAssessment | |||||||||||
| Short | A reference to data that supports this section | ||||||||||
| Definition | A reference to the actual resource from which the narrative in the section is derived. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(ClinicalImpression) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionFunctionalStatus.emptyReason | |||||||||||
| Short | Why the section is empty | ||||||||||
| Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | If a section is empty, why it is empty. | ||||||||||
| Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists. | ||||||||||
| Comments | The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionFunctionalStatus.section | |||||||||||
| Short | Nested Section | ||||||||||
| Definition | A nested sub-section within this section. | ||||||||||
| Cardinality | 0..0 | ||||||||||
| Type | see (section) | ||||||||||
| Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cmp-1 | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPastProblems | |||||||||||
| Short | IPS History of Past Problems Section | ||||||||||
| Definition | The History of Past Problems section contains a description of the conditions the patient suffered in the past but no longer tracked in the Problem List. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | BackboneElement | ||||||||||
| Must Support | True | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionPastProblems.id | |||||||||||
| Short | Unique id for inter-element referencing | ||||||||||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPastProblems.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPastProblems.extension:section-note | |||||||||||
| Short | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Definition | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPastProblems.modifierExtension | |||||||||||
| Short | Extensions that cannot be ignored even if unrecognized | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Modifier | True | ||||||||||
| Summary | True | ||||||||||
| Alias | extensions, user content, modifiers | ||||||||||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPastProblems.title | |||||||||||
| Short | Label for section (e.g. for ToC) | ||||||||||
| Definition | The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | string | ||||||||||
| Must Support | True | ||||||||||
| Alias | header, label, caption | ||||||||||
| Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. | ||||||||||
| Comments | The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionPastProblems.code | |||||||||||
| Short | Classification of section (recommended) | ||||||||||
| Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | Classification of a section of a composition/document. | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Provides computable standardized labels to topics within the document. | ||||||||||
| Comments | The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Pattern | {
"coding": [
{
"system": "http://loinc.org",
"code": "11348-0"
}
]
} | ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionPastProblems.author | |||||||||||
| Short | Who and/or what authored the section | ||||||||||
| Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||||||||||
| Requirements | Identifies who is responsible for the content. | ||||||||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPastProblems.focus | |||||||||||
| Short | Who/what the section is about, when it is not about the subject of composition | ||||||||||
| Definition | The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Reference(Resource) | ||||||||||
| Comments | Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPastProblems.text | |||||||||||
| Short | Text summary of the section, for human interpretation | ||||||||||
| Definition | A human-readable narrative that contains the attested content of the section, used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | Narrative | ||||||||||
| Must Support | True | ||||||||||
| Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionPastProblems.mode | |||||||||||
| Short | working | snapshot | changes | ||||||||||
| Definition | How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | code | ||||||||||
| Binding | The processing mode that applies to this section. | ||||||||||
| Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. | ||||||||||
| Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPastProblems.orderedBy | |||||||||||
| Short | Order of section entries | ||||||||||
| Definition | Specifies the order applied to the items in the section entries. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | What order applies to the items in the entry. | ||||||||||
| Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. | ||||||||||
| Comments | Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPastProblems.entry | |||||||||||
| Short | Conditions the patient suffered in the past. | ||||||||||
| Definition | It contains a description of the conditions the patient suffered in the past. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Condition | DocumentReference) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Slicing | Unordered, Open, by resolve()(Profile) | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPastProblems.entry:pastProblem | |||||||||||
| Short | A reference to data that supports this section | ||||||||||
| Definition | A reference to the actual resource from which the narrative in the section is derived. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(ConditionUvIps) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPastProblems.emptyReason | |||||||||||
| Short | Why the section is empty | ||||||||||
| Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | If a section is empty, why it is empty. | ||||||||||
| Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists. | ||||||||||
| Comments | The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPastProblems.section | |||||||||||
| Short | Nested Section | ||||||||||
| Definition | A nested sub-section within this section. | ||||||||||
| Cardinality | 0..0 | ||||||||||
| Type | see (section) | ||||||||||
| Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cmp-1 | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPregnancyHx | |||||||||||
| Short | IPS History of Pregnancy Section | ||||||||||
| Definition | The history of pregnancy section shall contain information about whether the patient is currently pregnant or not. It may contain addition summarizing information about the outcome of earlier pregnancies. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | BackboneElement | ||||||||||
| Must Support | True | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionPregnancyHx.id | |||||||||||
| Short | Unique id for inter-element referencing | ||||||||||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPregnancyHx.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPregnancyHx.extension:section-note | |||||||||||
| Short | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Definition | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPregnancyHx.modifierExtension | |||||||||||
| Short | Extensions that cannot be ignored even if unrecognized | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Modifier | True | ||||||||||
| Summary | True | ||||||||||
| Alias | extensions, user content, modifiers | ||||||||||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPregnancyHx.title | |||||||||||
| Short | Label for section (e.g. for ToC) | ||||||||||
| Definition | The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | string | ||||||||||
| Must Support | True | ||||||||||
| Alias | header, label, caption | ||||||||||
| Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. | ||||||||||
| Comments | The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionPregnancyHx.code | |||||||||||
| Short | Classification of section (recommended) | ||||||||||
| Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | Classification of a section of a composition/document. | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Provides computable standardized labels to topics within the document. | ||||||||||
| Comments | The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Pattern | {
"coding": [
{
"system": "http://loinc.org",
"code": "10162-6"
}
]
} | ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionPregnancyHx.author | |||||||||||
| Short | Who and/or what authored the section | ||||||||||
| Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||||||||||
| Requirements | Identifies who is responsible for the content. | ||||||||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPregnancyHx.focus | |||||||||||
| Short | Who/what the section is about, when it is not about the subject of composition | ||||||||||
| Definition | The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Reference(Resource) | ||||||||||
| Comments | Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPregnancyHx.text | |||||||||||
| Short | Text summary of the section, for human interpretation | ||||||||||
| Definition | A human-readable narrative that contains the attested content of the section, used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | Narrative | ||||||||||
| Must Support | True | ||||||||||
| Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionPregnancyHx.mode | |||||||||||
| Short | working | snapshot | changes | ||||||||||
| Definition | How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | code | ||||||||||
| Binding | The processing mode that applies to this section. | ||||||||||
| Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. | ||||||||||
| Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPregnancyHx.orderedBy | |||||||||||
| Short | Order of section entries | ||||||||||
| Definition | Specifies the order applied to the items in the section entries. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | What order applies to the items in the entry. | ||||||||||
| Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. | ||||||||||
| Comments | Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPregnancyHx.entry | |||||||||||
| Short | Current pregnancy status and, optionally, information about the outcome of earlier pregnancies. | ||||||||||
| Definition | It contains information about whether the patient is currently pregnant or not. It may contain addition summarizing information about the outcome of earlier pregnancies. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(DocumentReference | Observation) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Slicing | Unordered, Open, by resolve()(Profile) | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPregnancyHx.entry:pregnancyStatus | |||||||||||
| Short | A reference to data that supports this section | ||||||||||
| Definition | A reference to the actual resource from which the narrative in the section is derived. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(ObservationPregnancyStatusUvIps) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPregnancyHx.entry:pregnancyOutcome | |||||||||||
| Short | A reference to data that supports this section | ||||||||||
| Definition | A reference to the actual resource from which the narrative in the section is derived. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(ObservationPregnancyOutcomeUvIps) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPregnancyHx.emptyReason | |||||||||||
| Short | Why the section is empty | ||||||||||
| Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | If a section is empty, why it is empty. | ||||||||||
| Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists. | ||||||||||
| Comments | The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPregnancyHx.section | |||||||||||
| Short | Nested Section | ||||||||||
| Definition | A nested sub-section within this section. | ||||||||||
| Cardinality | 0..0 | ||||||||||
| Type | see (section) | ||||||||||
| Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cmp-1 | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPatientStory | |||||||||||
| Short | IPS Patient Story Section | ||||||||||
| Definition | The section contains narrative text along with optional resources that express what matters to a patient. This may include needs, strengths, values, concerns and preferences to others providing support and care. The patient’s story, provided here, may be told by the patient or by a proxy. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | BackboneElement | ||||||||||
| Must Support | True | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionPatientStory.id | |||||||||||
| Short | Unique id for inter-element referencing | ||||||||||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPatientStory.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPatientStory.extension:section-note | |||||||||||
| Short | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Definition | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPatientStory.modifierExtension | |||||||||||
| Short | Extensions that cannot be ignored even if unrecognized | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Modifier | True | ||||||||||
| Summary | True | ||||||||||
| Alias | extensions, user content, modifiers | ||||||||||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPatientStory.title | |||||||||||
| Short | Label for section (e.g. for ToC) | ||||||||||
| Definition | The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | string | ||||||||||
| Must Support | True | ||||||||||
| Alias | header, label, caption | ||||||||||
| Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. | ||||||||||
| Comments | The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionPatientStory.code | |||||||||||
| Short | Classification of section (recommended) | ||||||||||
| Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | Classification of a section of a composition/document. | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Provides computable standardized labels to topics within the document. | ||||||||||
| Comments | The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Pattern | {
"coding": [
{
"system": "http://loinc.org",
"code": "81338-6"
}
]
} | ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionPatientStory.author | |||||||||||
| Short | Who and/or what authored the section | ||||||||||
| Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||||||||||
| Requirements | Identifies who is responsible for the content. | ||||||||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPatientStory.focus | |||||||||||
| Short | Who/what the section is about, when it is not about the subject of composition | ||||||||||
| Definition | The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Reference(Resource) | ||||||||||
| Comments | Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPatientStory.text | |||||||||||
| Short | Text summary of the section, for human interpretation | ||||||||||
| Definition | A human-readable narrative that contains the attested content of the section, used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | Narrative | ||||||||||
| Must Support | True | ||||||||||
| Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionPatientStory.mode | |||||||||||
| Short | working | snapshot | changes | ||||||||||
| Definition | How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | code | ||||||||||
| Binding | The processing mode that applies to this section. | ||||||||||
| Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. | ||||||||||
| Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPatientStory.orderedBy | |||||||||||
| Short | Order of section entries | ||||||||||
| Definition | Specifies the order applied to the items in the section entries. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | What order applies to the items in the entry. | ||||||||||
| Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. | ||||||||||
| Comments | Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPatientStory.entry | |||||||||||
| Short | Patient Story resources. | ||||||||||
| Definition | Contains resources to support the Patient Story. Instances of DocumentReference or any other suitable resource type may be used. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Resource) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPatientStory.emptyReason | |||||||||||
| Short | Why the section is empty | ||||||||||
| Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | If a section is empty, why it is empty. | ||||||||||
| Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists. | ||||||||||
| Comments | The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPatientStory.section | |||||||||||
| Short | Nested Section | ||||||||||
| Definition | A nested sub-section within this section. | ||||||||||
| Cardinality | 0..0 | ||||||||||
| Type | see (section) | ||||||||||
| Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cmp-1 | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPlanOfCare | |||||||||||
| Short | IPS Plan of Care Section | ||||||||||
| Definition | The plan of care section contains a narrative description of the expectations for care including proposals, goals, and order requests for monitoring, tracking, or improving the condition of the patient. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | BackboneElement | ||||||||||
| Must Support | True | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionPlanOfCare.id | |||||||||||
| Short | Unique id for inter-element referencing | ||||||||||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPlanOfCare.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPlanOfCare.extension:section-note | |||||||||||
| Short | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Definition | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPlanOfCare.modifierExtension | |||||||||||
| Short | Extensions that cannot be ignored even if unrecognized | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Modifier | True | ||||||||||
| Summary | True | ||||||||||
| Alias | extensions, user content, modifiers | ||||||||||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPlanOfCare.title | |||||||||||
| Short | Label for section (e.g. for ToC) | ||||||||||
| Definition | The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | string | ||||||||||
| Must Support | True | ||||||||||
| Alias | header, label, caption | ||||||||||
| Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. | ||||||||||
| Comments | The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionPlanOfCare.code | |||||||||||
| Short | Classification of section (recommended) | ||||||||||
| Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | Classification of a section of a composition/document. | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Provides computable standardized labels to topics within the document. | ||||||||||
| Comments | The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Pattern | {
"coding": [
{
"system": "http://loinc.org",
"code": "18776-5"
}
]
} | ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionPlanOfCare.author | |||||||||||
| Short | Who and/or what authored the section | ||||||||||
| Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||||||||||
| Requirements | Identifies who is responsible for the content. | ||||||||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPlanOfCare.focus | |||||||||||
| Short | Who/what the section is about, when it is not about the subject of composition | ||||||||||
| Definition | The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Reference(Resource) | ||||||||||
| Comments | Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPlanOfCare.text | |||||||||||
| Short | Text summary of the section, for human interpretation | ||||||||||
| Definition | A human-readable narrative that contains the attested content of the section, used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | Narrative | ||||||||||
| Must Support | True | ||||||||||
| Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionPlanOfCare.mode | |||||||||||
| Short | working | snapshot | changes | ||||||||||
| Definition | How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | code | ||||||||||
| Binding | The processing mode that applies to this section. | ||||||||||
| Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. | ||||||||||
| Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPlanOfCare.orderedBy | |||||||||||
| Short | Order of section entries | ||||||||||
| Definition | Specifies the order applied to the items in the section entries. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | What order applies to the items in the entry. | ||||||||||
| Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. | ||||||||||
| Comments | Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPlanOfCare.entry | |||||||||||
| Short | Optional entry used to represent structured care plans | ||||||||||
| Definition | Dynamic, personalized plan including identified needed healthcare activity, health objectives and healthcare goals, relating to one or more specified health issues in a healthcare process [Source EN ISO 13940] | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(CarePlan | DocumentReference | ImmunizationRecommendation) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Slicing | Unordered, Open, by resolve()(Profile) | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPlanOfCare.entry:carePlan | |||||||||||
| Short | A reference to data that supports this section | ||||||||||
| Definition | A reference to the actual resource from which the narrative in the section is derived. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(CarePlan) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPlanOfCare.entry:immunizationRecommendation | |||||||||||
| Short | A reference to data that supports this section | ||||||||||
| Definition | A reference to the actual resource from which the narrative in the section is derived. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(ImmunizationRecommendation) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPlanOfCare.emptyReason | |||||||||||
| Short | Why the section is empty | ||||||||||
| Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | If a section is empty, why it is empty. | ||||||||||
| Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists. | ||||||||||
| Comments | The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionPlanOfCare.section | |||||||||||
| Short | Nested Section | ||||||||||
| Definition | A nested sub-section within this section. | ||||||||||
| Cardinality | 0..0 | ||||||||||
| Type | see (section) | ||||||||||
| Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cmp-1 | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionSocialHistory | |||||||||||
| Short | IPS Social History Section | ||||||||||
| Definition | The social history section contains a description of the person’s Health related "lifestyle factors" or "lifestyle observations" (e.g. smoke habits; alcohol consumption; diets, risky habits.) | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | BackboneElement | ||||||||||
| Must Support | True | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionSocialHistory.id | |||||||||||
| Short | Unique id for inter-element referencing | ||||||||||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionSocialHistory.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionSocialHistory.extension:section-note | |||||||||||
| Short | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Definition | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionSocialHistory.modifierExtension | |||||||||||
| Short | Extensions that cannot be ignored even if unrecognized | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Modifier | True | ||||||||||
| Summary | True | ||||||||||
| Alias | extensions, user content, modifiers | ||||||||||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionSocialHistory.title | |||||||||||
| Short | Label for section (e.g. for ToC) | ||||||||||
| Definition | The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | string | ||||||||||
| Must Support | True | ||||||||||
| Alias | header, label, caption | ||||||||||
| Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. | ||||||||||
| Comments | The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionSocialHistory.code | |||||||||||
| Short | Classification of section (recommended) | ||||||||||
| Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | Classification of a section of a composition/document. | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Provides computable standardized labels to topics within the document. | ||||||||||
| Comments | The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Pattern | {
"coding": [
{
"system": "http://loinc.org",
"code": "29762-2"
}
]
} | ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionSocialHistory.author | |||||||||||
| Short | Who and/or what authored the section | ||||||||||
| Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||||||||||
| Requirements | Identifies who is responsible for the content. | ||||||||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionSocialHistory.focus | |||||||||||
| Short | Who/what the section is about, when it is not about the subject of composition | ||||||||||
| Definition | The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Reference(Resource) | ||||||||||
| Comments | Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionSocialHistory.text | |||||||||||
| Short | Text summary of the section, for human interpretation | ||||||||||
| Definition | A human-readable narrative that contains the attested content of the section, used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | Narrative | ||||||||||
| Must Support | True | ||||||||||
| Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionSocialHistory.mode | |||||||||||
| Short | working | snapshot | changes | ||||||||||
| Definition | How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | code | ||||||||||
| Binding | The processing mode that applies to this section. | ||||||||||
| Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. | ||||||||||
| Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionSocialHistory.orderedBy | |||||||||||
| Short | Order of section entries | ||||||||||
| Definition | Specifies the order applied to the items in the section entries. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | What order applies to the items in the entry. | ||||||||||
| Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. | ||||||||||
| Comments | Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionSocialHistory.entry | |||||||||||
| Short | Health related "lifestyle factors" or "lifestyle observations" (e.g. smoke habits; alcohol consumption; diets, risky habits.) | ||||||||||
| Definition | Description of the person’s Health related “lifestyle factors" or "lifestyle observations" (e.g. smoke habits; alcohol consumption; diets, risky habits.) | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(DocumentReference | Observation) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Slicing | Unordered, Open, by resolve()(Profile) | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionSocialHistory.entry:smokingTobaccoUse | |||||||||||
| Short | A reference to data that supports this section | ||||||||||
| Definition | A reference to the actual resource from which the narrative in the section is derived. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Reference(ObservationTobaccoUseUvIps) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionSocialHistory.entry:alcoholUse | |||||||||||
| Short | A reference to data that supports this section | ||||||||||
| Definition | A reference to the actual resource from which the narrative in the section is derived. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Reference(ObservationAlcoholUseUvIps) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionSocialHistory.emptyReason | |||||||||||
| Short | Why the section is empty | ||||||||||
| Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | If a section is empty, why it is empty. | ||||||||||
| Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists. | ||||||||||
| Comments | The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionSocialHistory.section | |||||||||||
| Short | Nested Section | ||||||||||
| Definition | A nested sub-section within this section. | ||||||||||
| Cardinality | 0..0 | ||||||||||
| Type | see (section) | ||||||||||
| Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cmp-1 | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionVitalSigns | |||||||||||
| Short | IPS Vital Signs Section | ||||||||||
| Definition | The Vital signs section includes blood pressure, body temperature, heart rate, and respiratory rate. It may also include other clinical findings, such as height, weight, body mass index, head circumference, and pulse oximetry. In particular, notable vital signs or physical findings such as the most recent, maximum and/or minimum, baseline, or relevant trends may be included | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | BackboneElement | ||||||||||
| Must Support | True | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionVitalSigns.id | |||||||||||
| Short | Unique id for inter-element referencing | ||||||||||
| Definition | Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | string | ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionVitalSigns.extension | |||||||||||
| Short | Additional content defined by implementations | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Slicing | Unordered, Open, by url(Value) Extensions are always sliced by (at least) url | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionVitalSigns.extension:section-note | |||||||||||
| Short | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Definition | Additional notes that apply to the section (but not to specific resource). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Alias | extensions, user content | ||||||||||
| Comments | This extension SHALL NOT be used if the resource already has standard 'note' element (or equivalent) of type Annotation on the same element | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionVitalSigns.modifierExtension | |||||||||||
| Short | Extensions that cannot be ignored even if unrecognized | ||||||||||
| Definition | May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself). | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Extension | ||||||||||
| Modifier | True | ||||||||||
| Summary | True | ||||||||||
| Alias | extensions, user content, modifiers | ||||||||||
| Requirements | Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. | ||||||||||
| Comments | There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionVitalSigns.title | |||||||||||
| Short | Label for section (e.g. for ToC) | ||||||||||
| Definition | The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | string | ||||||||||
| Must Support | True | ||||||||||
| Alias | header, label, caption | ||||||||||
| Requirements | Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. | ||||||||||
| Comments | The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. Most Implementation Guides will make section title to be a required element. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionVitalSigns.code | |||||||||||
| Short | Classification of section (recommended) | ||||||||||
| Definition | A code identifying the kind of content contained within the section. This must be consistent with the section title. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | Classification of a section of a composition/document. | ||||||||||
| Must Support | True | ||||||||||
| Requirements | Provides computable standardized labels to topics within the document. | ||||||||||
| Comments | The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Pattern | {
"coding": [
{
"system": "http://loinc.org",
"code": "8716-3"
}
]
} | ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionVitalSigns.author | |||||||||||
| Short | Who and/or what authored the section | ||||||||||
| Definition | Identifies who is responsible for the information in this section, not necessarily who typed it in. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | ||||||||||
| Requirements | Identifies who is responsible for the content. | ||||||||||
| Comments | References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionVitalSigns.focus | |||||||||||
| Short | Who/what the section is about, when it is not about the subject of composition | ||||||||||
| Definition | The actual focus of the section when it is not the subject of the composition, but instead represents something or someone associated with the subject such as (for a patient subject) a spouse, parent, fetus, or donor. If not focus is specified, the focus is assumed to be focus of the parent section, or, for a section in the Composition itself, the subject of the composition. Sections with a focus SHALL only include resources where the logical subject (patient, subject, focus, etc.) matches the section focus, or the resources have no logical subject (few resources). | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | Reference(Resource) | ||||||||||
| Comments | Typically, sections in a doument are about the subject of the document, whether that is a patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionVitalSigns.text | |||||||||||
| Short | Text summary of the section, for human interpretation | ||||||||||
| Definition | A human-readable narrative that contains the attested content of the section, used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. | ||||||||||
| Cardinality | 1..1 | ||||||||||
| Type | Narrative | ||||||||||
| Must Support | True | ||||||||||
| Comments | Document profiles may define what content should be represented in the narrative to ensure clinical safety. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Obligations |
| ||||||||||
| Composition.section:sectionVitalSigns.mode | |||||||||||
| Short | working | snapshot | changes | ||||||||||
| Definition | How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | code | ||||||||||
| Binding | The processing mode that applies to this section. | ||||||||||
| Requirements | Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. | ||||||||||
| Comments | This element is labeled as a modifier because a change list must not be misunderstood as a complete list. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionVitalSigns.orderedBy | |||||||||||
| Short | Order of section entries | ||||||||||
| Definition | Specifies the order applied to the items in the section entries. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | What order applies to the items in the entry. | ||||||||||
| Requirements | Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. | ||||||||||
| Comments | Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionVitalSigns.entry | |||||||||||
| Short | Notable vital signs or physical findings. | ||||||||||
| Definition | Notable vital signs or physical findings as: blood pressure, body temperature, heart rate, and respiratory rate. It may also include other clinical findings, such as height, weight, body mass index, head circumference, and pulse oximetry. In particular, notable vital signs or physical findings such as the most recent, maximum and/or minimum, baseline, or relevant trends may be included | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(DocumentReference | Observation) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Slicing | Unordered, Open, by resolve()(Profile) | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionVitalSigns.entry:vitalSign | |||||||||||
| Short | A reference to data that supports this section | ||||||||||
| Definition | A reference to the actual resource from which the narrative in the section is derived. | ||||||||||
| Cardinality | 0..* | ||||||||||
| Type | Reference(observation-vitalsigns) | ||||||||||
| Comments | If there are no entries in the list, an emptyReason SHOULD be provided. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionVitalSigns.emptyReason | |||||||||||
| Short | Why the section is empty | ||||||||||
| Definition | If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason. | ||||||||||
| Cardinality | 0..1 | ||||||||||
| Type | CodeableConcept | ||||||||||
| Binding | If a section is empty, why it is empty. | ||||||||||
| Requirements | Allows capturing things like "none exist" or "not asked" which can be important for most lists. | ||||||||||
| Comments | The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: ele-1, cmp-2 | ||||||||||
| Constraints |
| ||||||||||
| Mappings |
| ||||||||||
| Composition.section:sectionVitalSigns.section | |||||||||||
| Short | Nested Section | ||||||||||
| Definition | A nested sub-section within this section. | ||||||||||
| Cardinality | 0..0 | ||||||||||
| Type | see (section) | ||||||||||
| Comments | Nested sections are primarily used to help human readers navigate to particular portions of the document. | ||||||||||
| Conditions | The cardinality or value of this element may be affected by these constraints: cmp-1 | ||||||||||
| Mappings |
| ||||||||||