#3: Patient Demographics DB

Document Actions

Collect all data objects and attributes here. Data Dictionary and Entity Relation Diagram. Notes and remarks

Proposed by

Lemoene Smit

Proposal type

Architecture

Assigned to release

Bika Health 1.0

State

being-discussed

Definitions

Sponsor

Ope Odusan, Advanta Laboratories

OpenMRS

Open Sourced Medical Record keeping framework. http://openmrs.org/

OpenMRS models apllied here:

http://openmrs.org/wiki/OpenMRS_data_model

http://openmrs.org/wiki/Image:Openmrs_data_model_1.00.png

Motivation

Developing a SQL back-end to production quality would take 4 months and probably longer. SQLAlchemy.org, 'The Python SQL Toolkit and Object Relational Mapper', seems to be the route to go. There is also Storm by Canonical

We want to be sure that Bika Health still runs on native ZODB for smaller installations, but that an SQL DB of choice can be swopped in with minimum effort. We start Bika Health development on the ZODB with added Patient object(s) and convert when SQL is available

To this purpose we adhere to open medical health record standards by OpenMRS as far possible

Assumptions

Proposal

Initial collection of DB properties here

Map sponsor requirement to that of OpenMRS and hand over to technical designers

Implementation

Omissions and some modifications were necessary to fit the sponsor requirement to the OpenMRS model

Only 1 patient name will be allowed, and the Patient and Patient Name tables will be mapped to the standard Plone Contact object

The OpenMRS multiple identifiers for patients are maintained, for ID, passport and driver's license numbers

The Address table inherits the title Location from OpenMRS but i can see this renamed when mapped to standard Plone objects, where field naming convention might differ too
All audit logging will be handled by standard Bika/Plone functionality

Extra

Guarantor, who would make payments on the patient's behalf. They share Identifier Types and Addresses 'tables' with Patient
Patient telephone, mobile and email address

Patient feature - for keeping descriptions and digital images of tribal markings, birth marks and scars

Other DB features and gaps identified

Ordering Physician/Hospital will map to current Bika 2 Client

Analyse services might have to be grouped into categories for display on request forms. In the lab itself these will be applied as the new Bika 2 Analysis profiles

The Sample object needs Sample date, Sampled by

Analysis Request form

Billing information - Patient / Insurance / Physician / other. This one affects Invoicing too

Remarks field for 'Relevant clinical data'

Deliverables

Patient demographics Entity Relation Diagram (ERD) and Data Dictionary (DD)

First drafts uploaded here

ERD: http://www.bikalabs.com/softwarecenter/bikahealth/roadmap/3/patienterd/view

DD: http://www.bikalabs.com/softwarecenter/bikahealth/roadmap/3/patientdd/view

Risks

Progress log

2007 07 21

First drafts uploaded, more texts to this page - lemoene

Post to Developer & User lists

To do

FOSS Health

Post to OpenMRS

Participants

Ope Odusan - Advanta Laboratories

lemoene Smit

Jacob Tekane

Anneline Sweetnam

Bika developer and user lists

Posts to OpenMRS lists

Bika Lab Systems

Sections

Personal tools