HL7 Czech Laboratory Order IG
0.0.1 - ci-build Czechia flag

HL7 Czech Laboratory Order IG, published by HL7 Czech Republic. This guide is not an authorized publication; it is the continuous build for version 0.0.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7-cz/lab-order/ and changes regularly. See the Directory of published versions

Logical Model: LabOrderDataElementsCz - Detailed Descriptions

Page standards status: Draft Maturity Level: 1

Definitions for the LabOrderDataElementsCz logical model.

Guidance on how to interpret the contents of this table can be foundhere

0. LabOrderDataElementsCz
Definition

Laboratory order data elements

ShortA.2.8 - Laboratory order data elements
Control0..*
Is Modifierfalse
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. LabOrderDataElementsCz.examination
Definition

A.2.8.1 - Required examinations

ShortA.2.8.1 - Required examinations
Control0..*
TypeBackboneElement
Invariantsele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count()))
4. LabOrderDataElementsCz.examination.id
Definition

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

ShortUnique id for inter-element referencing
Control0..1
Typestring
Is Modifierfalse
XML FormatIn the XML format, this property is represented as an attribute.
Summaryfalse
6. LabOrderDataElementsCz.examination.extension
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.

ShortAdditional content defined by implementations
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.

Control0..*
TypeExtension
Is Modifierfalse
Summaryfalse
Alternate Namesextensions, user content
Invariantsele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count()))
ext-1: Must have either extensions or value[x], not both (extension.exists() != value.exists())
SlicingThis element introduces a set of slices on LabOrderDataElementsCz.examination.extension. The slices areUnordered and Open, and can be differentiated using the following discriminators:
  • value @ url
  • 8. LabOrderDataElementsCz.examination.modifierExtension
    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).

    ShortExtensions that cannot be ignored even if unrecognized
    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.

    Control0..*
    TypeExtension
    Is Modifiertrue because Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
    Summarytrue
    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.

    Alternate Namesextensions, user content, modifiers
    Invariantsele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count()))
    ext-1: Must have either extensions or value[x], not both (extension.exists() != value.exists())
    10. LabOrderDataElementsCz.examination.code
    Definition

    A code representing an examination within an agreed codebook.

    • Preffered system(s): NČLP
    ShortA.2.8.1.1 - Examination code
    Control1..1
    TypeCodeableConcept
    12. LabOrderDataElementsCz.examination.name
    Definition

    Full name of the examination according to the codebook used.

    • Preffered system(s): NČLP
    ShortA.2.8.1.2 - Name of examination
    Control1..1
    TypeCodeableConcept
    14. LabOrderDataElementsCz.examination.procedure
    Definition

    Required examination procedure (measurement principle).

    • Preffered system(s): SNOMED CT
    • Preffered system(s): NČLP - NCLPPROC
    ShortA.2.8.1.3 - Examination procedure
    Control0..1
    TypeCodeableConcept
    16. LabOrderDataElementsCz.examination.accreditation
    Definition

    Requirement that only laboratories accredited for the test be able to perform the test.

    ShortA.2.8.1.4 - Accreditation
    Control0..1
    TypeCodeableConcept
    18. LabOrderDataElementsCz.examination.urgency
    Definition

    The urgency of the requested examination (vital indication, statim, priority (fast track), routine) if different from the urgency of the entire order.

    • Preffered system(s): HL7:RequestPriority
    • Preffered system(s): LOUP
    ShortA.2.8.1.5 - Urgency
    Control0..1
    TypeCodeableConcept
    20. LabOrderDataElementsCz.examination.note
    Definition

    Client's note on the requested examination

    ShortA.2.8.1.6 - Note
    Control0..1
    Typestring
    Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
    22. LabOrderDataElementsCz.examination.clinicalEvent
    Definition

    Information about the clinical event to which the ordered examination relates

    ShortA.2.8.1.7 - Clinical event (encounter)
    Control0..1
    Typehttps://hl7.cz/fhir/lab-order/StructureDefinition/ClinicalEventCz

    Guidance on how to interpret the contents of this table can be foundhere

    0. LabOrderDataElementsCz
    Definition

    Laboratory order data elements

    ShortA.2.8 - Laboratory order data elements
    Logical ModelInstances of this logical model are not marked to be the target of a Reference
    2. LabOrderDataElementsCz.examination
    Definition

    A.2.8.1 - Required examinations

    ShortA.2.8.1 - Required examinations
    Control0..*
    TypeBackboneElement
    4. LabOrderDataElementsCz.examination.code
    Definition

    A code representing an examination within an agreed codebook.

    • Preffered system(s): NČLP
    ShortA.2.8.1.1 - Examination code
    Control1..1
    TypeCodeableConcept
    6. LabOrderDataElementsCz.examination.name
    Definition

    Full name of the examination according to the codebook used.

    • Preffered system(s): NČLP
    ShortA.2.8.1.2 - Name of examination
    Control1..1
    TypeCodeableConcept
    8. LabOrderDataElementsCz.examination.procedure
    Definition

    Required examination procedure (measurement principle).

    • Preffered system(s): SNOMED CT
    • Preffered system(s): NČLP - NCLPPROC
    ShortA.2.8.1.3 - Examination procedure
    Control0..1
    TypeCodeableConcept
    10. LabOrderDataElementsCz.examination.accreditation
    Definition

    Requirement that only laboratories accredited for the test be able to perform the test.

    ShortA.2.8.1.4 - Accreditation
    Control0..1
    TypeCodeableConcept
    12. LabOrderDataElementsCz.examination.urgency
    Definition

    The urgency of the requested examination (vital indication, statim, priority (fast track), routine) if different from the urgency of the entire order.

    • Preffered system(s): HL7:RequestPriority
    • Preffered system(s): LOUP
    ShortA.2.8.1.5 - Urgency
    Control0..1
    TypeCodeableConcept
    14. LabOrderDataElementsCz.examination.note
    Definition

    Client's note on the requested examination

    ShortA.2.8.1.6 - Note
    Control0..1
    Typestring
    Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
    16. LabOrderDataElementsCz.examination.clinicalEvent
    Definition

    Information about the clinical event to which the ordered examination relates

    ShortA.2.8.1.7 - Clinical event (encounter)
    Control0..1
    Typehttps://hl7.cz/fhir/lab-order/StructureDefinition/ClinicalEventCz

    Guidance on how to interpret the contents of this table can be foundhere

    0. LabOrderDataElementsCz
    Definition

    Laboratory order data elements

    ShortA.2.8 - Laboratory order data elements
    Control0..*
    Is Modifierfalse
    Logical ModelInstances of this logical model are not marked to be the target of a Reference
    2. LabOrderDataElementsCz.examination
    Definition

    A.2.8.1 - Required examinations

    ShortA.2.8.1 - Required examinations
    Control0..*
    TypeBackboneElement
    Invariantsele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count()))
    4. LabOrderDataElementsCz.examination.id
    Definition

    Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

    ShortUnique id for inter-element referencing
    Control0..1
    Typestring
    Is Modifierfalse
    XML FormatIn the XML format, this property is represented as an attribute.
    Summaryfalse
    6. LabOrderDataElementsCz.examination.extension
    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.

    ShortAdditional content defined by implementations
    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.

    Control0..*
    TypeExtension
    Is Modifierfalse
    Summaryfalse
    Alternate Namesextensions, user content
    Invariantsele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count()))
    ext-1: Must have either extensions or value[x], not both (extension.exists() != value.exists())
    SlicingThis element introduces a set of slices on LabOrderDataElementsCz.examination.extension. The slices areUnordered and Open, and can be differentiated using the following discriminators:
    • value @ url
    • 8. LabOrderDataElementsCz.examination.modifierExtension
      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).

      ShortExtensions that cannot be ignored even if unrecognized
      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.

      Control0..*
      TypeExtension
      Is Modifiertrue because Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
      Summarytrue
      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.

      Alternate Namesextensions, user content, modifiers
      Invariantsele-1: All FHIR elements must have a @value or children (hasValue() or (children().count() > id.count()))
      ext-1: Must have either extensions or value[x], not both (extension.exists() != value.exists())
      10. LabOrderDataElementsCz.examination.code
      Definition

      A code representing an examination within an agreed codebook.

      • Preffered system(s): NČLP
      ShortA.2.8.1.1 - Examination code
      Control1..1
      TypeCodeableConcept
      12. LabOrderDataElementsCz.examination.name
      Definition

      Full name of the examination according to the codebook used.

      • Preffered system(s): NČLP
      ShortA.2.8.1.2 - Name of examination
      Control1..1
      TypeCodeableConcept
      14. LabOrderDataElementsCz.examination.procedure
      Definition

      Required examination procedure (measurement principle).

      • Preffered system(s): SNOMED CT
      • Preffered system(s): NČLP - NCLPPROC
      ShortA.2.8.1.3 - Examination procedure
      Control0..1
      TypeCodeableConcept
      16. LabOrderDataElementsCz.examination.accreditation
      Definition

      Requirement that only laboratories accredited for the test be able to perform the test.

      ShortA.2.8.1.4 - Accreditation
      Control0..1
      TypeCodeableConcept
      18. LabOrderDataElementsCz.examination.urgency
      Definition

      The urgency of the requested examination (vital indication, statim, priority (fast track), routine) if different from the urgency of the entire order.

      • Preffered system(s): HL7:RequestPriority
      • Preffered system(s): LOUP
      ShortA.2.8.1.5 - Urgency
      Control0..1
      TypeCodeableConcept
      20. LabOrderDataElementsCz.examination.note
      Definition

      Client's note on the requested examination

      ShortA.2.8.1.6 - Note
      Control0..1
      Typestring
      Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
      22. LabOrderDataElementsCz.examination.clinicalEvent
      Definition

      Information about the clinical event to which the ordered examination relates

      ShortA.2.8.1.7 - Clinical event (encounter)
      Control0..1
      Typehttps://hl7.cz/fhir/lab-order/StructureDefinition/ClinicalEventCz