Hi everyone. Please see the attached graphic (only the units area for this thread). Let me know if you want to work on this project!
Workflows
Team
Chatroom
#inpatient
4 Likes
@MatthewVita So you know I am 75% done with institutional UB04/CMS-1450 claim module aimed at institutions.
2 Likes
That is very encouraging!
this is how I imagine the first screen. it is almost exactly we find in every intensive care unit in Brazil, but handmade, on whiteboard. thoughts on it:
- multitask feature (e.g. lab test for patients 1, 4 and 5)
- a ânew patientâ link, with option to import from other sources, like patient portal, or other facilities
1 Like
we could walk by the suggested features @MatthewVita pointed, what do you guys think?
1 Like
UPDATES:
- We should include the MAR work by @robert.down and @juggernautsei in this project. Very important for inpatient.
- It may be interesting to work with the MohawkMEDIC client-registry team to get an EMPI solution documented in the case a hospital uses multiple medical systems. I recently got in touch with them as I am interested in how to integrate the solution with OpenEMR. This may be more for US use cases though
UPDATES:
- I have asked @andremillet to look into the following:
- Amazon Fire 8" for each bed
- Cheap, but good medical devices (EKG, heart rate, etc) - Maybe even RaspPI https://image.slidesharecdn.com/ganeshbhorrasberrypi-160328181339/95/raspberry-pi-technology-19-638.jpg?cb=1459193559
- Affordable tablet medical carts
- A related inpatient feature-set discussion just popped up: OpenEMR for everything
kindle done
raspPI FTW
who made this
1 Like
Just found on Google. Not sure of the source 
It will be a good unit testing to access openEmr from the Fire HD8 and see how the stable and the beta openEmr version works. Obrigado Andre.
1 Like
is from my-sygnals.com. the email I just told you about.
1 Like
If it matters, Iâve done considerable micro controller design and firmware development including Linux driver development for many micro controllers including RaspPI and T.I. Most emphasis on real world interfaces and protocol stacks.
2 Likes
welcome to the team !
@sjpadgett Hi Jerry. I also want to welcome you to the team.
It appears that the research @andremillet did with the my signals devices company has concluded with the following results:
- The devices are very nice and cost effective, but only really work with their proprietary âcpuâ system that is costly
- The company has an older âcpuâ system that would be cheaper, but it doesnât look like they make it anymore.
To jump on a task, please engage with the following issue: Low Cost Medical Devices Search for OpenEMR Integration · Issue #978 · openemr/openemr · GitHub (this is where we are recording our progress)
See the task entited " Look for low cost EKG and Pulse Oximeter/Blood Oxygen devices that are either usb devices or RaspPis that work with cheap Android tablets or Windows netbooks." - this may be a good one to pick up on as Andre and I await a final response from my signals company.
1 Like
I have many of the micro controllers you have been looking at and what you are paying for really is the firmware to run the sensors/devices. I need to do some research and get back to you. In the end, you should not be too worried about processing cost but concentrate on the peripheral devices. Especially those that may already have A/D and digital interfaces.
1 Like
Agree that peripheral devices are the big focus.
Note that I have redid this threadâs initial post to be specific to units. Devices and other inpatient features will be handled in other threads.
1 Like