Is there a Bed management module in the RefApp (or planned for OpenMRS 3?) It appears that Bahmni has a Bed Management module and there are previous threads about this.
If not, has anyone used other software for this (ie. CommCare) to replace a paper-based “system”? Has anyone used Bahmni’s bed management along with all other functionality using the RefApp?
@mksd I have a project where I actually want to use O3 but it looks like it is still lacking the Bed Management which Bahmni has. I need it finished in around half a year but would like to align design with the community instead of just forking the Bahmni Bed Management UI. Since mekom is involved in the Squad O3 IPD Inpatient Department Requirements - Projects - OpenMRS Wiki I thought we can discuss and align before we start anything on our own.
Hi @johnny94, good to hear from you, it’s been a while!
Yes I would definitely encourage you to go with O3 and its new IPD features. However they will be released soon, they haven’t been released yet. You may be able to check them out on a dev or staging server at this point. Maybe @vasharma05 or @usamakakumba could point you to some environment for taking a peak?
The bed management module, the backend one, is also used to support the configuration of wards and beds, etc. This is shared with Bahmni.
Happy to connect next week if you wish. It’s indeed important that we understand your requirements to ensure proper alignment of your work with the community.
I actually have not yet special requirements for IPD but I need the essential features which look super promising (Bed assignment, Transfer to other Locations, Admission Queue, etc. are working)
I would still like to connect when I have something more specific!
My usual requirements like Audit Log and Radiology should be worked on as well as is can see - maybe you have here as well an opinion on it
Indeed I refer to the thread you pointed to. I can only repeat that we should resume the work that was started (a long time ago by @wyclif) and ensure that there is an official Audit Log module that everyone can rely upon, and that becomes part of the default O3 distro.
Integration with PACS
This is IMO undoubtedly an Ozone topic, as all facility-level point-to-point integrations should be. For example, Ozone 1.0.0-alpha.12 will include basic support for OpenMRS-Orthanc integration by incorporating Orthanc as an app within the Ozone ecosystem. Looking ahead, we aim to enable OpenMRS-dcm4chee integration by similarly incorporating dcm4chee (and related tools, such as WEASIS) as part of the Ozone ecosystem of apps, provided budget, roadmap, and priorities allow.
@johnny94 I’m pretty tied up with a proposal until the end of next week but…
After that, I’ll post about the work we’ve done with Orthanc, including a demo video. It’s pretty basic at this point, and yet it provides a starter for PACS-related workflows within Ozone. Or maybe @sidvaish97 perhaps could prepare a draft post already?
One thing to know about Orthanc though, is that it’s a bit of a pure PACS with no concept of radiology orders (my understanding at least, Siddharth / @weisadre to confirm).
We definitely want to offer the option within Ozone to spin up dcm4chee as well and to expand the current EMR-PACS data flows to involve radiology orders coming from the EMR app. Perhaps something we could do together?
I think it is a good idea to collaborate on the EMR-PACS for O3 - maybe we can start with discussing key business requirements and come up with a architecture draft.
You can reach me on Slack @jbravo94 whenever you have time.