0.1.0 - ci-build
KenyaDiagnosticsFHIRIG - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.
| Kenya Diagnostics IG Capability Statement |
Defines the expected capabilities of this IG. |
These define constraints on FHIR resources for systems conforming to this implementation guide.
| KenyaDiagnosticReport |
This profile defines a diagnostic report to be used in a laboratory test. |
| KenyaDiagnosticServiceRequest |
This profile defines a service request to be used in a laboratory test. |
| KenyaEncounter |
This profile defines an encounter that resulted in a laboratory test. |
| KenyaHealthProviderOrganization |
Profile for an Organization with an MFL code as the primary identifier. |
| KenyaObservation |
This profile defines an observation to be used in a laboratory test. |
| KenyaSpecimen |
This profile defines a specimen for a laboratory test. |
| Patient (IPS) |
This profile represents the constraints applied to the Patient resource by the International Patient Summary (IPS) FHIR Implementation Guide and describes the minimum expectations for the Patient resource when used in the IPS composition or in one of the referred resources. |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| Extension for rejection reasons for lab orders |
Extension for rejection reasons for lab orders |
| Service Request Cost |
An extension to represent the cost of a service in a ServiceRequest. |
These define sets of codes used by systems conforming to this implementation guide.
| ValueSet: Justification options for Lab Orders |
Justification options for lab orders in this IG |
| ValueSet: Rejection reasons for Lab Orders |
Rejection reasons for lab orders in this IG |
| Yes/No Value Set |
The SNOMED CT codes to answer in the affirmative or negative. |
These define new code systems used by systems conforming to this implementation guide.
| CodeSystem: Laboratory Order Justifications |
The reason for ordering a laboratory test. |
| CodeSystem: Laboratory Order Rejection Reasons |
The reason for rejecting a laboratory Order. |
| KMHFL Code System |
The KMHFL code system is a code system that defines the KMHFL identifier. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| cbc-diagnostic-report |
An example of a diagnostic report for complete blood count (CBC). |
| cbc-lab-request |
An example of a laboratory test request for complete blood count (CBC). |
| cbc-observation |
An example of a blood specimen. |
| cbc-patient |
An example of a patient. |
| cbc-specimen |
An example of a blood specimen. |
| cgrh-organization-example |
Example of an organization that is responsible for a laboratory test. |
| drtb-lab-request |
An example of a laboratory test request for drug resistance to tuberculosis (DR-TB). |
| drtb-patient |
An example of a patient. |
| drtb-specimen |
An example of a blood specimen. |
| example-patient-2 |
An example of a patient. |
| jootrh-organization-example |
Example of an organization that is responsible for a laboratory test. |
| ntrl-organization-example |
Example of an organization. |
| vl-hiv-diagnostic-report |
An example of a diagnostic report for HIV viral load. |
| vl-hiv-lab-request |
Example of a laboratory test request for HIV viral load. |
| vl-hiv-observation |
An example of a HIV viral load observation. |