Tip |
---|
|
...
Parameter | [A] Custom Dictionary | [B] CIEL Dictionary | [C] SNOMED TS backed dictionary (with Bahmni custom dictionary as Base) | [D] SNOMED TS backed dictionary (with CIEL dictionary as Base) | |||||
---|---|---|---|---|---|---|---|---|---|
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/ |
|
| ||||
2 | How do I browse this dictionary online? | Browse the concept dictionary on our demo server here: demo.mybahmni.org (superman/Admin123) | (Same as prev column) | ||||||
3 | Which option is used most frequently in the real world with Bahmni? | Majority of the real world deployments of Bahmni (until v0.93) before Bahmni Lite have used a Custom Dictionary. | Since Bahmni Lite v1.0 release in June2023, new adopters have started evaluating / adopting CIEL dictionary. CIEL is being used with OpenMRS already in many real world settings. | SNOMED CT is used widely in many EHRs across the world. With Bahmni, since this is a recent development, we don’t yet have any known real-world deployment of Bahmni-SNOMED TS directly. | (Same as prev column) | ||||
4 | Which configuration of Bahmni comes out-of-the-box with this option? | default-config (currently default for Bahmni-Standard for Hospitals) | clinic-config (with Bahmni Lite) | snomed-default-config (with Bahmni Lite & SNOMED configuration) | snomed-clinic-config(with Bahmni Lite and SNOMED Configuration). Has some known issues, see this link. | ||||
5 | How do I report a term that should be present in standard dictionary but it somehow isn’t? | You can add it yourself. | Drop an email to Dr. Andrew Kanter from CIEL | Inform SNOMED international, or check if your country has already added it in the country specific extensions. | (Same as prev column) | ||||
6 | Can I use OCL (Open Concept Lab) to manage terms? | Yes | Yes. Bahmni ships the CIEL zip file that is released via OCL. | No, the SNOMED-TS (terminology server) acts as the TS here. In this configuration OCL is not involved. | (Same as prev column) | ||||
7 | While recording Diagnosis in Bahmni what terms will I see on the UI? | Your custom terms | CIEL terms or any custom terms added by you to the Concept Dictionary. |
| (Same as prev column) | ||||
8 | For recording Chief Complaints in Bahmni what terms will I see? | Your custom terms | CIEL terms or any custom terms added by you to the Concept Dictionary. | Search results are constrained using a SNOMED “ECL query”, specified in the form designer for Chief Complaints in the H&E form. Currently configured same as all Clinical Findings. See documentation. | (Same as prev column) | ||||
9 | For recording Drugs in Bahmni what terms will I see? |
|
|
| (Same as prev column) | ||||
10 | What terms can I use in the Form Designer for Questions/Answers? | Your custom terms can be used. | Any CIEL dictionary or custom added term can be used. |
| (Same as prev column) | ||||
11 | Can I use my own custom terms along with this option? | Yes. | Yes, but recommend checking with Dr. Andrew Kanter, who maintains CIEL dictionary if the term can be added to standard CIEL distribution. |
| (Same as prev column) | ||||
12 | How are conflicts in Concept Names handled (when a custom concept is also present)? | You cannot add two concepts with the same FSN. | You cannot add two concepts with the same FSN. |
| (Same as prev column) | ||||
13 | Will I be able to record data in SNOMED CT? | If you define reference mappings for a term in SNOMED CT, you should be able to create reports in SNOMED CT (but not see anything in SNOMED CT on screen). | CIEL dictionary has defined SNOMED reference maps for many most terms, and you should be able to create an SQL report based on that data. On screen, you would still see CIEL terms. |
| (Same as prev column) | ||||
14 | Will I be able to use Bahmni’s custom CDS integration over FHIR? (More details on Clinical Decision Support - CDS feature see this documentation and video) |
|
|
| (Same as prev column) | ||||
15 | Will be be able to use Hierarchical reporting to aggregate specific diseases into a parent group easily? | No, since Hierarchical reporting needs SNOMED Terminology Server configuration. | No, since Hierarchical reporting needs SNOMED Terminology Server configuration. | Yes. Ability to create out-of-box reports quickly are available. See this documentation. | (Same as prev column) | ||||
16 | Will I be able to use Bahmni ICD10 reporting feature? |
|
| Yes | (Same as prev column) | ||||
17 | Can I use this option in an offline / on-premise installation of Bahmni? | Yes | Yes |
| (Same as prev column) | ||||
18 | Is there any performance impact? | No,as data is locally stored in Bahmni. | No, as data is locally stored in Bahmni. |
| (Same as prev column) | ||||
19 | Migrate to another terminology set? | Will require migration effort if shifting to CIEL or SNOMED CT. | Will require significant migration effort if shifting to SNOMED CT. | Shifting to a different terminology system will require significant migration effort. | (Same as prev column) | ||||
20 | Is there a docker-compose option available that packages this set out-of-the-box for me to try? | Yes. bahmni-standard. | Yes. bahmni-lite | Yes. See snomed-bahmni-docker repository (with snomed-default-config configuration) | Yes. See snomed-bahmni-docker repository (with snomed-clinic-config configuration) | ||||
21 | If I use OpenELIS (Lab), or Odoo, or DCM4chee, will this option work? | Yes. | Yes | Not Recommended. Development & Testing required. | (Same as prev column), will this option work? | Yes. | No. Not yet tested. Only OpenMRS and Crater tested to work. | Yes. See JIRA-3453. Works for both, SNOWSTORM and SNOWSTORM-LITE. | No. Not tested. Will likely need some development & testing. |
22 | Can i use the Patient FHIR Export feature? | Yes | Yes | Yes | (Same as prev column) | ||||
23 | What competency is expected of the clinicians who will be recording this data? | They can use the same terms they currently use on Paper / hospital. | Will need to be familiar with CIEL terms (50k). | Will need to be familiar with SNOMED terms and ontology (300K terms). | (Same as prev column) | ||||
24 | Is this option FREE or PAID or OpenSource? | Free and Opensource | Free and Opensource. See this page. |
| (Same as prev column) | ||||
25 | How often does this option get updated with new terms? | You decide.Typically once every few months? | CIEL is updated monthly with more frequent updates in the cases of emergencies like COVID-19.See this page. | See Releases page on SNOMED. | (Same as prev column) | ||||
26 | Are other languages supported besides English? | Since this is your custom dictionary, you will need to enter & manage the translations. | Yes, other languages are also included in CIEL. Link? | In current integration, we have only added support for ENGLISH, even though SNOMED CT supports others locales. Supporting other languages will require some development efforts. Other languages are also included in SNOMED TS, typically in country extensions. SNOMED CT is a multinational, multilingual terminology. It has a built-in framework to manage different languages and dialects. The international browser has many national extensions loaded: See also: SNOMED CT Translation Tooling | (Same as prev column) | ||||
27 | What advantages will I get with this option? | You get full control with the terms you see on the screen, but you need to manage all the master data and reference maps yourself, which is tedious, and usually requires strong clinical terminology expertise. |
|
| (Same as prev column) | ||||
28 | What possible disadvantages I should consider with this option? | Tedious / error prone to use, or introduce terms later in the process. Requires strong terminology expertise. |
|
|
| ||||
29 | Any Other Information? | - | - | - | - |