Generated Narrative: StructureDefinition LabReport Name Flags Card. Type Description & Constraints LabReport 0..* Base A - Laboratory Report #xD; header 1..1 BackboneElement A.1 Report header data elements #xD; subject 1..1 Subject A.1.1 - A1.2 Patient/subject #xD; payer 0..1 Payer A.1.3 Health insurance and payment information #xD; informationRecipient 0..1 Recipient A.1.4 Information recipient #xD; author 0..* Author A.1.5 Author #xD; legalAuthenticator 0..* LegalAuthenticator A.1.6 Legal authenticator #xD; validator 0..* Validator A.1.7 Result validator #xD; metadata 1..1 BackboneElement A.1.8 Laboratory report metadata #xD; documentId 1..1 Identifier A.1.8.0 Document Id #xD; type 1..1 CodeableConcept A.1.8.1 Document type #xD; status 1..1 CodeableConcept A.1.8.2 Document status #xD; dateTime 1..1 dateTime A.1.8.3 Report date and time #xD; title 0..1 string A.1.8.4 Document title #xD; studyType 0..* CodeableConcept A.1.8.5 Study type #xD; custodian 0..1 BackboneElement A.1.8.6 Report custodian #xD; confidentiality 0..1 CodeableConcept A.1.8.7 Confidentiality #xD; language 0..1 CodeableConcept A.1.8.8 Language #xD; version 0..1 string A.1.8.9 Version #xD; order 0..* Order A.2-A.3 Order #xD; specimen 0..* SpecimenLab A.4 Specimen information #xD; result 0..* Result A.5 Results data elements #xD; Documentation for this format
Used by permission of HL7 Europe, all rights reserved Creative Commons License
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
A.1.1 Identification of the patient/subject and A.1.2 Patient/subject related contact information
A.1.3 Health insurance and payment information
A.1.4 Information recipient (intended recipient or recipients of the report, additional recipients might be identified by the ordering party, e.g. GP, other specialist), if applicable
A.1.5 Author (by whom the Laboratory result report or a subset of its results was authored)
A.1.6 Legal authenticator (The person taking responsibility for the medical content of the document)
A coded type of the document. Fixed value ""Laboratory report"" - Preferred system(s): LOINC
The status of the laboratory test result report. E.g., preliminary, final. - Preferred system(s): hl7:DiagnosticReportStatus
Date and time of the result report creation. - Preferred system(s): ISO 8601
Document title, e.g. 'Laboratory Result report'
Type (or types) of the laboratory study performed. - Preferred system(s): LOINC SNOMED CT
Organisation that is in charge of maintaining the laboratory report
Level of confidentiality of the document. Implicit value is normal. - Preferred system(s): hl7:Confidentiality
Language in which the document is written. Language is expressed by the ISO language code.- Preferred system(s): BCP 47
A.2 Order information (Laboratory Result Report could respond to multiple test orders) A.3 Order reason (Laboratory Result Report could respond to multiple reasons)