Notes from the Birds of a Feather session at OMRS17:
Bahmni and OCL Birds of Feather Session
Abhinav- 2018 create thinner size of Bahmni in vertical programs (NCDs, etc.). Want to access a set of concepts to support the vertical. Want to have an editor be able to build a collection from CIEL and have Bahmni download it from OCL. Eventually would like to have forms distributed. OCL would need to be able to support drug formulations. Pilot implementation in Jordan MSF (defined 10K concepts)
Sanjay- same use case but include NCD like Mental Health & Diabetes quality management. Used in secondary referral facility. Do we use UUID or concept_id
Deepak- Currently using concept_name to aggregate different servers. There is an endTB dictionary of 2500-3000 concepts shared with 25 sites. But there are 15-20 implementations with completely different concept dictionaries.
Possible health has 9000 concepts. Perhaps 1000 have CIEL maps. Need to cover all of First three digits for ICD-10-WHO reporting for IMS (insurance management system)
Darius- we need a clean subset to start new implementations, but we also need to have a process for migration of other sites (lesser priority). Need someone to build starter sets in OCL to exercise the process. Need to be able to “fork” copy core concept set to allow modification to update the SET (mostly add, but perhaps also remove). Pull changes not push them. Want to be able to have a collection of collections and not rely on CIEL’s set of sets approach. What are the missing concepts from
Jeremy- Interested in concept proposal methodology with updating. Need to have it visible to CIEL and would be nice to see the forms where it is used. Also interested in surgical procedures. Is there a starter set for surgical procedures.
Tim- Asked whether a subscription module could subscribe to more than one collection. Better to have reconciliation and duplicate checking done at the OCL level so not a need to have a subscription module be able to subscribe to more than one OCL collection. How does OCL help with data output to DHIS2, etc.? Discharge forms have diagnoses, operations performed, complication of anything that was done, and discharge status.
Required functionality content is one category, and subsets of content based upon vertical use cases. Latter should be based on frequency distribution or some value of use.
- Discharge Status
- Stopped Order Reason
Possible Health has added columns to the concept tables. Need to think about how data gets anonymized.