/
Modelling OpenMRS Encounters vs. FHIR Encounter resources

Modelling OpenMRS Encounters vs. FHIR Encounter resources

 

Scenario

User makes two different visits.

Visit A is an inpatient visit, and includes 5 encounters.

Visit B is an outpatient visit, and includes just one encounter.

Visit A
  • uuid x

  • Account no: 123

  • Admitting diagnosis: malaria

  • Discharge diagnosis: malaria

    • Encounter 1 (uuid 1)

    • Encounter 2 (uuid 2)

    • Encounter 3 (uuid 3)

    • Encounter 4 (uuid 4)

    • Encounter 5 (uuid 5)

Visit B
  • uuid y

  • Account no: 123

    • Encounter 6 (uuid 6)

 

Note:

In a practical scenario, outpatient visits will far outnumber inpatient visits.

Admitting diagnosis, discharge diagnosis and account number are all visit attributes, and represent how information can be attached to visit objects themselves.

How can users obtain this data ?

1) GET request for FHIR encounter with UUID x.

In this case, the UUID points to a visit, which groups 5 OpenMRS encounters

2) GET request for FHIR encounter with UUID 1.

 

3) GET request for FHIR encounter with UUID 6.

 

 

Related content

Encounter Resource
Encounter Resource
More like this
Sessions or Encounter Transactions (Design Page)
Sessions or Encounter Transactions (Design Page)
More like this
Demo FHIR Requests
Demo FHIR Requests
More like this
OpenMRS FHIR Module - Initial design
OpenMRS FHIR Module - Initial design
More like this
Patient Data Management OWA
Patient Data Management OWA
More like this
Proposed OpenMRS Domain Object to FHIR Resource Mapping
Proposed OpenMRS Domain Object to FHIR Resource Mapping
More like this