Versions Compared

Old Version 8

changes.mady.by.user Jackson Onyango

Saved on

compared with

New Version 9

changes.mady.by.user Eunice Njeri

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
outlinetrue
stylenone

Overview

OpenMRS currently contains a legacy model for the Encounters and Observationsmanaging patient data which includes modules for: patient details, visits,  encounters and observations.

These will be migrated to new OWA using ReactJS and combine the two onto one parent interface and toggle between them using two buttonsmake them connected to avoid the current separate user interfaces.

Definitions:

  • Encounter

...

  • Visit


Following a visit to the health clinic, patient may receive several kinds of care and services example: see a clinician, have an X-ray taken, and be given a lab test. These services once recorded in the electronic form make up the encounters. A visit can have one to several encounters. 
Therefore a visit can be viewed as the root of encounters and observations.

  • Encounter

An encounter can be defined as any interaction and includes doctor visits, laboratory tests, food distribution, home visits, etc. Encounters are typically represented as a form (consisting of hundreds of observations), but service or interaction at the health clinic that is filled in an electronic form .It could also be a touch-screen patient registration or a single lab test for CD4.

It can consist of zero to several observations.


  • Observation

Anything actively measured or observed during an encounter examples: patients' weights, heights, blood pressures, and BMIs are observations etc

 

scenarios showing visit, encounters,observation.

For more clarification of the above, check here

Why use these two modules?

  • These ensure we are able to track a patient's encounters or interactions with the hospital staff and monitor his health progress by using the observations recorded.

What The Module Does?

Encounter:

Allows one to perform CRUD operations by:

  • Manage(Add/View/Edit/Delete/Search)  Encounters
  • Manage(Add/View/Edit/Delete/Search) Encounter Types
  • Manage(Add/View/Edit/Delete/Search) Encounter Roles

Observation:

Allows one to perform CRUD operations by:

...

  • One visit with one encounter without observations – Touch screen patient registration in Haiti
  • One visit with one encounter with one observation – Touch screen patient registration in Rwinkwavu, Rwanda with weight recorded
  • One visit with one encounter and many observations – HIV followup form
  • One visit with multiple encounters and many observations – HIV followup form along with ART drug regimen pickup.  This would show 2 encounters, where each encounter would have a different encounter id and encounter type.

Purpose of this Module:

This module will ensure that we bring the currently separated modules together to ensure blissful experience for the user. 

Functionality Description:

Once logged in, a user will be able to search for a patient. 

Choose patient from the filtered list and will be redirected to a page consisting of that patient's details including:

  • identifiers
  • names
  • addresses
  • demographics
  • visits and encounters

On these, s/he will be able to manage this information by adding, editing, deleting and undeleting.


Developers:

Team Lead:

Developers:

...