Generated Narrative: StructureDefinition preeclampsia-referral Name Flags Card. Type Description & Constraints preeclampsia-referral 0..* Base Logical Model for Preeclampsia Referral in Antenatal Care Scenario patient 1..1 Reference(Patient) Reference to the pregnant patient encounter 1..1 Reference(Encounter) ANC visit encounter details observations 1..* BackboneElement Observations conducted during ANC visit bloodPressure 1..1 BackboneElement Blood Pressure Observation systolicBP 1..1 Reference(Systolic Blood Pressure (Observation)) Systolic Blood Pressure diastolicBP 1..1 Reference(Diastolic Blood Pressure (Observation)) Diastolic Blood Pressure urineProtein 1..1 Reference(Protein Urine (Observation)) Proteinuria test result temperature 1..1 Reference(Body Temperature (Observation)) Body Temperature condition 1..1 Reference(Condition) Diagnosis of preeclampsia serviceRequest 1..1 Reference(ServiceRequest) Urgent referral to hospital Documentation for this format
Logical Model for Preeclampsia Referral in Antenatal Care Scenario
Represents a scenario where a pregnant woman with preeclampsia is referred to a hospital.
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")])
Extensions that cannot be ignored even if unrecognized
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).
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](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them