Generated Narrative: StructureDefinition BeModelChildReport Name Flags Card. Type Description & Constraints BeModelChildReport 0..* BeModelDocument Child Report Logical Model Elements defined in Ancestors:subject, documentType, status, identifier, recordedDate, author[x], presentedForm, documentTitle, section Instances of this logical model can be the target of a Reference #xD; subject 1..1 BeModelPatient Child that the report is about #xD; recordedDate 1..1 dateTime The date when the document was last updated #xD; presentedForm 1..1 Attachment Child report PDF file #xD; pregnancyDetails 0..1 Base Pregnancy details #xD; durationOfPregnancy 0..1 Base [BeClinicalObservation] The duration of pregnancy in weeks, as an observation. #xD; subject 1..1 Reference() Child #xD; code 1..1 CodeableConcept Length of gestation at birth Required Pattern: At least the following #xD; coding 1..* Coding Code defined by a terminology system Fixed Value: (Complex) #xD; system 1..1 uri Identity of the terminology system Fixed Value: http://snomed.info/sct #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: 412726003 #xD; display 1..1 string Representation defined by the system Fixed Value: Length of gestation at birth #xD; valueInteger 1..1 integer The duration of pregnancy in weeks #xD; pregnancyCMVInfection 0..1 Base [BeClinicalObservation] Pregnancy CMV infection #xD; subject 1..1 Reference() Child #xD; code 1..1 CodeableConcept CMV infection during pregnancy Required Pattern: At least the following #xD; coding 1..* Coding Code defined by a terminology system Fixed Value: (Complex) #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: cmv-infection-during-pregnancy #xD; display 1..1 string Representation defined by the system Fixed Value: CMV infection during pregnancy #xD; valueBoolean 1..1 boolean Indicates whether CMV infection occurred during pregnancy. #xD; bacterialMeningitis 0..1 Base [BeClinicalObservation] Bacterial meningitis #xD; code 1..1 CodeableConcept Code Required Pattern: At least the following #xD; coding 1..* Coding Code defined by a terminology system Fixed Value: (Complex) #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: bacterial-meningitis-during-pregnancy #xD; display 1..1 string Representation defined by the system Fixed Value: bacterial meningitis during pregnancy #xD; subject 1..1 Reference() Child #xD; valueBoolean 1..1 boolean Indicates whether bacterial meningitis occurred during pregnancy. #xD; neonatalHearingScreeningLeft 0..1 Base [BeClinicalObservation] Left ear result #xD; date 1..1 date Date of neonatal hearing screening #xD; subject 1..1 Reference(BePatient) Child that the report is about #xD; code 1..1 CodeableConcept Result of neonatal hearing screening - left Required Pattern: At least the following #xD; coding 1..* Coding Code defined by a terminology system Fixed Value: (Complex) #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: neonatal-hearing-screening-left #xD; display 1..1 string Representation defined by the system Fixed Value: Result of neonatal hearing screening (left ear) #xD; valueCode 1..1 code Result of neonatal hearing screening (left ear) Binding: Neonatal Hearing Screening Results (required) #xD; neonatalHearingScreeningRight 0..1 Base [BeClinicalObservation] Right ear result #xD; date 1..1 date Date of neonatal hearing screening #xD; subject 1..1 Reference(BePatient) Child that the report is about #xD; code 1..1 CodeableConcept Result of neonatal hearing screening - right Required Pattern: At least the following #xD; coding 1..* Coding Code defined by a terminology system Fixed Value: (Complex) #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: neonatal-hearing-screening-right #xD; display 1..1 string Representation defined by the system Fixed Value: Result of neonatal hearing screening (right ear) #xD; valueCode 1..1 code Result of neonatal hearing screening (right ear) Binding: Neonatal Hearing Screening Results (required) #xD; severeHeadTrauma 0..1 Base [BeProblem] Severe head trauma #xD; subject 1..1 Reference(BePatient) Child that the report is about #xD; date 1..1 date Date of reporting the trauma. #xD; code 1..1 CodeableConcept Code Required Pattern: At least the following #xD; coding 1..* Coding Code defined by a terminology system Fixed Value: (Complex) #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: severe-head-trauma-during-delivery #xD; display 1..1 string Representation defined by the system Fixed Value: Severe head trauma #xD; valueBoolean 1..1 boolean Indicates whether severe head trauma was identified. #xD; eyeScreening 0..* BackboneElement [BeClinicalObservation] Eye screening #xD; subject 1..1 Reference(BePatient) Child that the report is about #xD; date 1..1 date Date of eye screening #xD; code 1..1 CodeableConcept Code Required Pattern: At least the following #xD; coding 1..* Coding Code defined by a terminology system Fixed Value: (Complex) #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: eye-screening #xD; display 1..1 string Representation defined by the system Fixed Value: Eye screening findings #xD; valueCodeableConcept 1..1 code Result of eye screening Binding: Eye Screening Results (required) #xD; eyeResults 0..* Base Eye #xD; inspectionPupilAbnormal 0..1 BackboneElement [BeClinicalObservation] Inspection pupil abnormal #xD; subject 1..1 Reference(BePatient) Child that the report is about #xD; date 1..1 date Date of abnormal pupil inspection finding #xD; code 1..1 CodeableConcept Inspection pupil abnormal Required Pattern: At least the following #xD; coding 1..* Coding Code defined by a terminology system Fixed Value: (Complex) #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: inspection-pupil-normal #xD; display 1..1 string Representation defined by the system Fixed Value: Inspection pupil abnormal #xD; valueBoolean 1..1 boolean Inspection pupil abnormal #xD; eyeMovementAndPosition 0..* BackboneElement [BeClinicalObservation] Findings about the eye movement and position #xD; subject 1..1 Reference(BePatient) Child that the report is about #xD; date 1..1 date Date of eye movement and position results #xD; code 1..1 CodeableConcept Code Required Pattern: At least the following #xD; coding 1..* Coding Code defined by a terminology system Fixed Value: (Complex) #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: eye-movement-and-position #xD; display 1..1 string Representation defined by the system Fixed Value: Eye movement and position #xD; valueCode 1..1 code Result of testing eye movement and position Binding: Eye Movement and Position (required) #xD; eyeRemarks 0..1 BackboneElement [BeClinicalObservation] Eye remarks #xD; subject 1..1 Reference(BePatient) Child that the report is about #xD; date 1..1 date Date of eye remarks #xD; code 1..1 CodeableConcept Eye remark Required Pattern: At least the following #xD; coding 1..* Coding Code defined by a terminology system Fixed Value: (Complex) #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: eye-remarks #xD; display 1..1 string Representation defined by the system Fixed Value: Eye remarks #xD; valueString 1..1 string Eye remarks #xD; inTreatmentWithOphthalmologist 0..* BackboneElement [BeClinicalObservation] In treatment with ophthalmologist #xD; date 1..1 date Date of remarks about treatment with ophthalmologist. #xD; code 1..1 CodeableConcept Code Required Pattern: At least the following #xD; coding 1..* Coding Code defined by a terminology system Fixed Value: (Complex) #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: in-treatment-with-ophtalmologist #xD; display 1..1 string Representation defined by the system Fixed Value: In treatment with ophthalmologist #xD; valueCode 1..1 code Treatment with ophthalmologist Binding: Ophthalmologist Treatments (required) #xD; Documentation for this format
A logical model representing child report data elements.
Type of the document, e.g. report, discharge letter, etc.
The date when the document was last updated
The date of the child report is the date when the report was created, not the date of the examination or observation. In case of reports migrated from KMEHR, the date is the date of the conversion, not the KMEHR message creation, which is unknown.
Author(s) by whom the resource was/were authored. Multiple authors could be provided.
A base64 encoded PDF file with the remaining child report information (biometric data, charts, etc.).
[BeClinicalObservation] The duration of pregnancy in weeks, as an observation.
[BeClinicalObservation] Pregnancy CMV infection
Indicates whether CMV infection occurred during pregnancy.
The value indicates whether the mother had a CMV infection during pregnancy.
[BeClinicalObservation] Bacterial meningitis
Indicates whether bacterial meningitis occurred during pregnancy.
The value indicates whether the mother had a bacterial meningitis during pregnancy.
Result of neonatal hearing screening for the left ear.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
SHALL have a contained resource if a local reference is provided
reference.startsWith('#').not() or (reference.substring(1).trace('url') in %rootResource.contained.id.trace('ids'))
not(starts-with(f:reference/@value, '#')) or exists(ancestor::*[self::f:entry or self::f:parameter]/f:resource/f:*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')]|/*/f:contained/f:*[f:id/@value=substring-after(current()/f:reference/@value, '#')])
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")])
Literal reference, Relative, internal or absolute URL
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.
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.
Type the reference refers to (e.g. "Patient")
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).
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.
Aa resource (or, for logical models, the URI of the logical model).
Logical reference, when literal reference is not known
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.
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).
Plain text narrative that identifies the resource in addition to the resource reference.
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.
Result of neonatal hearing screening - left
Result of neonatal hearing screening (left ear)
Neonatal hearing screening result for the left ear.
[BeClinicalObservation] Right ear result
Result of neonatal hearing screening for the right ear.
Result of neonatal hearing screening - right
Result of neonatal hearing screening (right ear)
Neonatal hearing screening result for the right ear.
Indicates whether severe head trauma was identified.
The value indicates whether severe head trauma was identified in the child.
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
[BeClinicalObservation] Inspection pupil abnormal
Details about the inspection of the pupil.
Date of abnormal pupil inspection finding
Date of abnormal pupil inspection finding.
[BeClinicalObservation] Findings about the eye movement and position
Date of eye movement and position results
The date of eye movement and position results.
Result of testing eye movement and position
Result of testing eye movement and position.
[BeClinicalObservation] In treatment with ophthalmologist
Details about treatment with an ophthalmologist.
Date of remarks about treatment with ophthalmologist.