Generated Narrative: StructureDefinition OLCarerContingencyPlan Name Flags Card. Type Description & Constraints OLCarerContingencyPlan 0..* Element OL - Carer contingency plan Elements defined in Ancestors:@id, <a href="http://hl7.org/fhir/R4/datatypes.html#Element" title="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.">extension #xD; codedText 1..1 DvCodedText coded_text Binding: OL - Carer contingency plan: coded_text (required) #xD; <a href="StructureDefinition-OLCarerContingencyPlan-definitions.html#OLCarerContingencyPlan.composer" title="[RM] The person primarily responsible for the content of the Composition (but not necessarily its committal into the EHR system). This is the identifier which should appear on the screen. It may or may not be the person who entered the data. When it is the patient, the special self instance of `PARTY_SELF` will be used.">composer 1..1 PARTY_PROXY composer #xD; <a href="StructureDefinition-OLCarerContingencyPlan-definitions.html#OLCarerContingencyPlan.context" title="[at0002] `COMPOSITION.context` - Documents the context information of a healthcare event involving the subject of care and the health system. The context information recorded here are independent of the attributes recorded in the version audit, which document the system interaction context, i.e. the context of a user interacting with the health record system. Healthcare events include patient contacts, and any other business activity, such as pathology investigations which take place on behalf of the patient.">context 1..1 EVENT_CONTEXT Context #xD; startTime 1..1 DvDateTime start_time #xD; setting 1..1 DvCodedText setting Binding: OL - Carer contingency plan: setting (required) #xD; xDSMetadata 0..1 Cluster XDS Metadata #xD; authorSpecialty 0..1 DvText Author specialty #xD; classCode 0..1 DvText Class code #xD; documentType 0..1 DvText Document type #xD; confidentialityCode 0..1 DvText Confidentiality code #xD; healthCareFacilityType 0..1 DvText Health care facility type #xD; practiceSettingCode 0..1 DvText Practice setting code #xD; eventCode 0..* DvText Event code #xD; documentMedia 0..1 DvMultimedia Document_media #xD; careJourneyMetadata 0..1 Cluster Care journey metadata #xD; carePlanName 0..1 DvText Care plan name #xD; carePlanIdentifier[x] 0..1 Care plan identifier #xD; carePlanIdentifierDvText DvText #xD; carePlanIdentifierDvIdentifier DvIdentifier #xD; patientJourneyIdentifier[x] 0..1 Patient journey identifier #xD; patientJourneyIdentifierDvText DvText #xD; patientJourneyIdentifierDvIdentifier DvIdentifier #xD; PersonalResponsibilities 0..1 EVALUATION Personal responsibilities #xD; responsibilitiesStatus 0..1 DvCodedText Responsibilities status Binding: OL - Carer contingency plan: Responsibilities status (required) #xD; description 0..1 DvText Description #xD; primaryCarerParentalResponsibility 0..1 Cluster Primary carer /parental responsibility #xD; careContingencyPlanStatus 0..1 DvCodedText Care contingency plan status Binding: OL - Carer contingency plan: Care contingency plan status (required) #xD; caredForPerson 0..1 DvText Cared for person #xD; howLongCanTheyWaitOnTheirOwn 0..1 DvText How long can they wait on their own #xD; replacementCarer 0..1 Cluster Replacement carer #xD; member 0..1 Cluster Member #xD; relationship 0..* DvCodedText Relationship Binding: OL - Carer contingency plan: Relationship (preferred) #xD; primaryContact 0..* DvCodedText Primary contact Binding: OL - Carer contingency plan: Primary contact (required) #xD; supportContactType 0..* DvCodedText Support contact type Binding: OL - Carer contingency plan: Support contact type (required) #xD; additionalInformation 0..1 DvText Additional information #xD; membername 0..* Cluster Name #xD; use 1..1 DvCodedText Use Binding: OL - Carer contingency plan: Use (required) #xD; contactName 0..1 DvText Contact name #xD; telecomContact 0..* Cluster Telecom contact #xD; contactType 0..1 DvCodedText Contact type Binding: OL - Carer contingency plan: Contact type (required) #xD; contactValue 0..1 DvText Contact value #xD; address 0..* Cluster Address #xD; addressUse 0..1 DvCodedText Address Use Binding: OL - Carer contingency plan: Address Use (required) #xD; street 0..1 DvText Street #xD; street2 0..1 DvText Street2 #xD; city 0..1 DvText City #xD; county 0..1 DvText County #xD; postalCode 0..1 DvText Postal code #xD; country 0..1 DvText Country #xD; dateAdded 0..1 DvDateTime Date added #xD; hasThePersonConsentedToTheReplacement 0..1 DvCodedText Has the person consented to the replacement Binding: OL - Carer contingency plan: Has the person consented to the replacement (required) #xD; replacementHasConsentedToBeingContacted 0..1 DvCodedText Replacement has consented to being contacted Binding: OL - Carer contingency plan: Replacement has consented to being contacted (required) #xD; replacementHasConsentedToActingInThatRole 0..1 DvCodedText Replacement has consented to acting in that role Binding: OL - Carer contingency plan: Replacement has consented to acting in that role (required) #xD; replacementHasACopyOfContingencyPlan 0..1 DvCodedText Replacement has a copy of contingency plan Binding: OL - Carer contingency plan: Replacement has a copy of contingency plan (required) #xD; pet 0..* Cluster Pet #xD; petDetails 0..1 DvText Pet details #xD; dateLastUpdated 0..1 DvDateTime Date last updated #xD; Documentation for this format
[openEHR-EHR-COMPOSITION.anticipatory_care_information.v0] A framework to communicate information that has been captured and curated in anticipation of future need for care.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
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.
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.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
[RM] The person primarily responsible for the content of the Composition (but not necessarily its committal into the EHR system). This is the identifier which should appear on the screen. It may or may not be the person who entered the data. When it is the patient, the special self instance of `PARTY_SELF` will be used.
[at0002] `COMPOSITION.context` - Documents the context information of a healthcare event involving the subject of care and the health system. The context information recorded here are independent of the attributes recorded in the version audit, which document the system interaction context, i.e. the context of a user interacting with the health record system. Healthcare events include patient contacts, and any other business activity, such as pathology investigations which take place on behalf of the patient.
participations.exists() implies participations.empty().not()
location.exists() implies location.empty().not()
Start time of the clinical session or other kind of event during which a provider performs a service of any kind for the patient.
Optional end time of the clinical session.
The actual location where the session occurred, e.
The actual location where the session occurred, e.g. 'microbiology lab 2', 'home', 'ward A3' and so on.
[RM] The setting in which the clinical session took place. Coded using the openEHR Terminology, setting group.
Other optional context which will be archetyped.
The health care facility under whose care the event took place.
The health care facility under whose care the event took place. This is the most specific workgroup or delivery unit within a care delivery enterprise that has an official identifier in the health system, and can be used to ensure medico-legal accountability.
Parties involved in the healthcare event.
Parties involved in the healthcare event. These would normally include the physician(s) and often the patient (but not the latter if the clinical session is a pathology test for example).
[RM] COMPOSITION.context.start_time - Start time of the clinical session or other kind of event during which a provider performs a service of any kind for the patient.
[openEHR-EHR-CLUSTER.xds_metadata.v0] Additional composition metadata aligned with IHE-XDS which is not already available from the Reference Model COMPOSITION class.
links.exists() implies links.empty().not()
Archetyped valid must satisfy exclusive conditions
is_archetype_root() xor archetype_details .empty()
Archetype node id valid must not be empty
Runtime name of this fragment, used to build runtime paths.
Runtime name of this fragment, used to build runtime paths. This is the term provided via a clinical application or batch process to name this EHR construct: its retention in the EHR faithfully preserves the original label by which this entry was known to end users.
Design-time archetype identifier of this node taken from its generating archetype; used to build archetype paths.
Design-time archetype identifier of this node taken from its generating archetype; used to build archetype paths. Always in the form of an at-code, e.g. `at0005`. This value enables a 'standardised' name for this node to be generated, by referring to the generating archetype local terminology. At an archetype root point, the value of this attribute is always the stringified form of the `_archetype_id_` found in the `_archetype_details_` object.
Optional globally unique object identifier for root points of archetyped structures.
Links to other archetyped structures (data whose root object inherits from `ARCHETYPED`, such as `ENTRY`, `SECTION` and so on).
Links to other archetyped structures (data whose root object inherits from `ARCHETYPED`, such as `ENTRY`, `SECTION` and so on). Links may be to structures in other compositions.
Details of archetyping used on this node.
Audit trail from non-openEHR system of original commit of information forming the content of this node, or from a conversion gateway which has synthesised this node.
Ordered list of items - `CLUSTER` or `ELEMENT` objects - under this `CLUSTER`.
[at0001] The speciality of the author/composer of the document.
[at0002] A high-level document class code, normally selected from a valueset provided by the IHE-XDS Affinity Domain.
[at0003] The code specifying the precise type of document from the user perspective. Normally selected from a valueset provided by the local IHE-XDS Affinity Domain or national standard.
[at0004] A term specifying the level of confidentiality of the XDS Document.
[at0007] A term defining the healthcare facility type.
[at0009] The code specifying the clinical specialty where the act that resulted in the document was performed.
[at0011] This list of codes represents the main clinical acts.
[at0010] Additional metadata about the document itself, including size, url.
[openEHR-EHR-CLUSTER.care_journey_metadata.v0] Tp capture Care plan metadata
[at0001] The name , preferably coded of the Care plan with which this journey is associated, and against which the composition was updated.
at0002: The identifier , preferably coded, of the Care plan with which this journey is associated, and against which the composition was updated.
at0003: A patient-journey specific identifier i.e unique to a patient's journey along a specific care pathway.
[openEHR-EHR-EVALUATION.personal_responsibilities.v1] Personal responsibilities
Subject validity must satisfy conditional constraints
subject_is_self() implies subject.generating_type = “PARTY_SELF”
Other participations valid must be present
other_participations.exists() implies other_participations.empty().not()
Mandatory indicator of the localised language in which this Entry is written.
Mandatory indicator of the localised language in which this Entry is written. Coded from openEHR Code Set languages .
Name of character set in which text values in this Entry are encoded.
Name of character set in which text values in this Entry are encoded. Coded from openEHR Code Set character sets.
Identifier of externally held workflow engine data for this workflow execution, for this subject of care.
Id of human subject of this `ENTRY`, e.g.: * organ donor * foetus * a family member * another clinically relevant person.
Optional identification of provider of the information in this `ENTRY`, which might be: * the patient * a patient agent, e.
Optional identification of provider of the information in this `ENTRY`, which might be: * the patient * a patient agent, e.g. parent, guardian * the clinician * a device or software Generally only used when the recorder needs to make it explicit. Otherwise, Composition composer and other participants are assumed.
Description of the method (i.e. how) the information in this entry was arrived at. For `OBSERVATIONs`, this is a description of the method or instrument used. For `EVALUATIONs`, how the evaluation was arrived at. For `INSTRUCTIONs`, how to execute the Instruction. This may take the form of references to guidelines, including manually followed and executable; knowledge references such as a paper in Medline; clinical reasons within a larger care process.
Optional external identifier of guideline creating this Entry if relevant.
The data of this evaluation, in the form of a spatial data structure.
[openEHR-EHR-CLUSTER.contact_cc.v0] Contacts for patients and organisations (excluding practitioners).
[at0001] The relationship between the subject and the contact. This field is only appropriate when the archetype is used for patient contacts, not for organisation contacts.
[at0013] Indicates a purpose for which the contact can be reached. This field is only appropriate when the archetype is used inside an organisation cluster.
[openEHR-EHR-CLUSTER.name_cc.v0] Name details aligned with FHIR resource.
[at0001] Identification of the purpose for the name.
[at0009] A text representation of the full name.
[openEHR-EHR-CLUSTER.telecom_cc.v0] FHIR telecom details.
[at0001] Telecommunications form for contact point - what communications system is required to make use of the contact.
[at0002] The actual contact point details, in a form that is meaningful to the designated communication system (i.e. phone number or email address).
[openEHR-EHR-CLUSTER.address_cc.v0] Address details aligned with FHIR resource.
[at0011] This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information.
[at0012] The name of the city, town, village or other community or delivery center.
[at0013] The name of the administrative area (county).
[at0014] A postal code designating a region defined by the postal service.
[at0015] Country - a nation as commonly understood or generally accepted.
[at0011] Date and time when contact detail starts to be valid.
Has the person consented to the replacement
Replacement has consented to being contacted
Replacement has consented to acting in that role
Replacement has a copy of contingency plan