Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

This page is a work-in -progress.

...

  1. Current SHR and Use Case and Requirements for OpenHIE ( we will need to include the CBR use case in this document to ensure that we are aligned with what the SHR needs)

  2. CBR Use Case

    1. This use case assumes that the CBR is using OpenMRS ( and the OpenMRS metadata model) for the SHR

      1. https://wiki.ohie.org/display/SUB/OpenMRS+as+the+SHR+design+document

    2. A point-of-care system (e.g. OpenMRS) should generate a standard CBR, transmit via defined messaging protocols and be received and consumed by OpenHIE. OpenHIE will be able to consume and store a normalised subset of clinical/ CBR information items (that which is deemed appropriate to share based on defined privacy constraints) from the patient’s CBR within the OpenHIE.

    3. Data will be parsed and stored within the Shared Health Record structure and will include the following patient and clinical domains:

      1. Specific data domains to be stored ( and eventually queried)  include but are not limited to the following:

        1. Patient demographics

        2. HIV Status

          1. Including WHO staging

        3. Medications

          1. Type

          2. Date of initiation

        4. HIV test results (CD4 and Viral Load)

          1. Including testing date

        5. Pregnancy Status

        6. Diagnoses ( in addition to HIV)

        7. Death ( date and cause)

      2. Unstructured data along with associated metadata, e.g. a PDF document or digital image with attached patient demographic information will be stored within the SHR

...