[bika-dev] Bika Health. Patient demographics

[bika - l. <le...@bi...>]

Dear all

We updated the Bika Health project page - www.bikalabs.com/health - with 
draft design for the Patient Demographics required by Ope, using 
OpenMRS' design for medical record keeping. Please see the proposal at 
http://www.bikalabs.com/softwarecenter/bikahealth/roadmap/3

Please comment/suggest

Release 1 information can be found at 
http://www.bikalabs.com/softwarecenter/bikahealth/releases/1.0

bests, lemoene
www.bikalabs.com


Technical extract:

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

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, etc

    * 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 Address  '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'


First drafts uploaded

Entity Relation Diagram (ERD) 
http://www.bikalabs.com/softwarecenter/bikahealth/roadmap/3/patienterd/view

Data Dictionary (DD) 
http://www.bikalabs.com/softwarecenter/bikahealth/roadmap/3/patientdd/view


OpenMRS models at

http://openmrs.org/wiki/OpenMRS_data_model

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