HL7 Czech K-Order Implementation Guide
0.0.3 - ci-build
HL7 Czech K-Order Implementation Guide
0.0.3 - ci-build
HL7 Czech K-Order Implementation Guide, published by HL7 Czech Republic. This guide is not an authorized publication; it is the continuous build for version 0.0.3 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7-cz/k-order/ and changes regularly. See the Directory of published versions
This page lists HL7 FHIR logical models used to represent the K-ORDERS.
To facilitate the references with the eHN data sets the short description of each element reports the label of the eHN element (e.g., A.1.7.2 Result validator name).
The HL7 FHIR logical model requires that element cardinality is specified, while the eHN data set doesn't define them on purpose. For this reason the elements' cardinality of the following FHIR Logical Model should be interpreted with this in mind, thus they should not be considered as "normative".
| Name | Title | Description |
| LogEnKOrderHeaderCz | A.1 Order header data elements | Order header data elements |
| LogEnSubjectKOrderCz | A.1.1 - Identification and A.1.2 - related contact information of the Patient/subject | Order - Order subject data element - A.1.1 and A.1.2 |
| LogEnPayerOrderKOrderCz | A.1.3 - Health insurance and payment information | Health insurance and payment information - Health insurance information is not always required, however, in some jurisdictions, the insurance number is also used as the patient identifier. It is necessary not just for identification but also forms access to funding for care. |
| LogEnCoverageKOrderCz | A.1.4 - Information about coverage | Coverage information - Information about method of coverage, payer identification data and additional information |
| LogEnAuthorKOrderCz | A.1.5 - Author | Author (by whom the Lab order was/were authored). Multiple authors could be provided. |
| LogEnRequestedPerformerKOrderCz | A.1.6 - Requested Performer (processing person) | Person who is requested to process document. |
| LogEnAdditionalRecipientKOrderCz | A.1.7 - Additional Recipient | Additional Recipient (Additional recipients of the finding in addition to the author) |
| LogEnDocumentMetadataKOrderCz | A.1.8 - Document metadata | Document metadata |
| LogEnDigitalSignatureKOrderCz | A.1.9 - Digital signature | Digital signature - Electronic signature or seal of a document according to Act 327/2011 §54a |
| LogEnBodyKOrder | A.2 – Document Body | Body of the K-order document containing clinical data, diagnoses, clinical reasons for the request, and specification of requested examinations and procedures. |
| LogEnKOrderInformationCz | A.2.1 - Order information and A.2.2 - Order reason | Information about order and order reason |
| LogEnClinicalReasonKOrderCZ | A.2.2 – Clinical reason for the request | Clinical reasons for the consultation request or other healthcare service request, including medical history, objective findings, and other related clinical information. |
| LogEnRequestedServiceKOrder | A.2.3 – Requested examinations / procedures | Specification of requested consultative examinations, treatments, or medical procedures. |
| LogEnRecommendationKOrder | A.2.4 – Recommendation | Recommendation of further management, transfer of care, or hospitalization. |
| LogEnAdditionalClinicalInfoKOrderCZ | A.2.5 – Additional Clinical Information | Additional clinical information and notes related to the consultation request (K-order). |
| LogEnAttachmentsCz | A.5 - Additional attachments | K-Order additional attachments - A.4 |
| LogEnPresentedFormCz | A.5 - Presented form | Presented form - Entire report as issued. Various formats could be provided, pdf format is recommended. |