This page lists down the various options for Concept Dictionary data setup and their pros/cons and provides some parameters to help make a decision.
Parameter | Custom Dictionary | CIEL Dictionary | SNOMED TS backed dictionary (with custom concepts) | SNOMED TS backed dictionary (with CIEL) | |
|---|---|---|---|---|---|
| 1 | Brief Overview | In this option you are choosing to run Bahmni with a custom concept dictionary that contains clinical terms decided by you (and your clinical terminology team). | In this option you are choosing to load Bahmni with publicly available and opensource CIEL dictionary comprising of 50K+ terms with SNOMED, ICD10, LOINC, RxNorm reference mappings, already done. The Bahmni Concept Dictionary will be loaded with CIEL data and you will use CIEL Terms to record data on the Bahmni UI. For more details see: https://openconceptlab.org/2022/10/19/ciel-bridging-terminology-for-the-global-community/ | In this option you are choosing to load Bahmni with few custom concepts and also connecting it to SNOMED Terminology Server, which will act as a real-time terminology server. You are going to use SNOMED CT terms on Bahmni UI to record clinical data. Whenever a SNOMED term is chosen on the UI, that term is pulled into Bahmni, and stored into the Concept Dictionary. So, over time, Bahmni concept dictionary starts reflecting a list of your facility commonly used clinical terms. For more details see this wiki page. SNOMED CT has over 300K clinical terms. | Similar to prev column, but Bahmni concept dictionary is pre-loaded with CIEL data. For most operations you will still be using SNOMED CT terms on the Bahmni UI for recording data. |
| 2 | Which option is used most frequently in the real world with Bahmni? | ||||
| 3 | Which configuration of Bahmni comes out-of-the-box with this option? | ||||
| 4 | Can I use custom terms along with this option? | ||||
| 5 | How do I report a term that should be present in standard dictionary but it somehow isn’t? | ||||
| 6 | Can I use OCL (Open Concept Lab) to manage terms? | ||||
| 7 | For recording diagnosis in Bahmni what terms will I see? | ||||
| 8 | For recording Chief Complaints in Bahmni what terms will I see? | ||||
| 9 | For recording Drugs in Bahmni what terms will I see? | ||||
| 10 | Will I be able to report data in SNOMED CT? | ||||
| 11 | Will I be able to use Bahmni’s custom CDSS integration over FHIR? | ||||
| 12 | Will I be able to use Bahmni ICD10 reporting feature? | ||||
| 13 | Will be be able to use Hierarchical reporting to aggregate specific diseases into a parent group easily? | ||||
| 14 | Can I use this option in an offline / on-premise installation of Bahmni? | ||||
| 15 | Is there any performance impact? | ||||
| 16 | Migrate to another terminology set? | ||||
| 17 | Is there a docker-compose option available that packages this set out-of-the-box for me to try? | ||||
| 18 | If I use OpenELIS (Lab), or Odoo, or DCM4chee, will this option work? | ||||
| 19 | Can i use the Patient FHIR Export feature? | ||||
| 20 | What competency is expected of the clinicians who will be recording this data? | ||||
| 21 | Is this option FREE or PAID or OpenSource? | ||||
| 22 | How often does this option get updated with new terms? | ||||
| 23 | What advantages will I get with this option? | ||||
| 24 | What possible disadvantages I should consider with this option? | ||||
| 25 | Any Other Information? | ||||
| 26 |