This is the FHIR Implementation Guide for Case Reporting containing the specifications developed by the OpenHIE community.

• This implementation guide and set of artifacts are still undergoing development.
• This content is only for demonstration purposes only.
• Providing Feedback: Please submit any issues via the Feedback link next to the appropriate section of the implementation guide

Summary

This Implementation Guide contains the full set of specifications for the Vietnam HIV case reporting. It is based on the specifications provided by the Case Reporting Implementation Guide and the baseline HIV Case Reporting Content specifications, adding the Vietnam specific implementation aspects.

This Implementation Guide is underpinned by supporting guidelines, policies and recommendations

This Implementation Guide defines three actors involved in the submission of a case report into a case report repository. These actors engage in the transactions to submit, transform and store case reports into a case report repository.

About This Implementation Guide

This Implementation Guide is broken into the following levels of knowledge representation:

• Level I: Narrative Contains references to the guidance, guidlines, policies and recommemndations underpinning this Implementation Guide
• ​Level II: Business Requirements Contains the requirements for this Implementation Guide including the defintition of key concepts, user personas, use cases and workflows.
• Level III: Data Models and Exchange Contains the data models and data exchange protocols defined in this Implementation Guide.
• ​Level IV - ε: Deployment Guidance Contains Instant OpenHIE Technical Specifications relevant to this Implementation Guide and supporting guidance for adaptation in local environments.

Intellectual Property Considerations

While this implementation guide and the underlying FHIR are licensed as public domain, this guide may include examples making use of terminologies such as LOINC, SNOMED CT and others which have more restrictive licensing requirements. Implementers should make themselves familiar with licensing and any other constraints of terminologies, questionnaires, and other components used as part of their implementation process. In some cases, licensing requirements may limit the systems that data captured using certain questionnaires may be shared with.

Disclaimer

The specification herewith documented is a demo working specification, and may not be used for any implementation purposes. This draft is provided without warranty of completeness or consistency, and the official publication supersedes this draft. b No liability can be inferred from the use or misuse of this specification, or its consequences.