Thank you for sharing your progress with this project! I've worked in Epic and Cerner my entire career, but not in a programming capacity. I set up the billing tables and revenue workflows, then troubleshoot charges. But it's still so fascinating to see how these programs can be built from the ground up!
Great Work Sidharth, Dr. Poornachandra and Medblocks Team 💪🏾 You are definitely attacking the pain points of the monoliths. Being able to customize data collection to your work flow and making that data actionable is a huge win👏
I'm a med student currently pursuing my internship and I have always thought EHR is going to be a big thing in the future. Especially a modular and DIY kind of EHR could help so many clinicians in both small setups and large hospitals. It could even fuel a new revolution in medical research bringing unexpected correlations between health interventions and outcomes. This has so much untapped potential. Feels really great to see someone making innovation in the field. All the best guys. I hope I can work for you someday.
Hi Sidharth/Poorna, this is a good start. I have some feedback that will be too much to type. Please leave me a message or you have my co-ordinates, if you want to reach out. But in general I would like to ask are you going to restrict this to BCVA/refraction/prescription glasses for ophthalmology ? Sounds like no, with the use of SNOMED-CT as in the demo. I don't see a viewer in this. OCT, FAF, CFP, MP and others are too important if you would like to make it more robust. Most of this is proprietary and not DICOM, although some of them can be DICOM extracted. Right now there are a combination of solutions being worked out. Would be interesting to discuss further
Hey Venu, we have integrated most of the imaging through a SMART app given the patient ID. For eg. we use EIDON (non-mydriatic cams) for every patient, and this is just another iFrame within the patient context. We are yet to strongly link DICOM and structured data capture, but a lot of DICOM viewers do support "context based launch" - where you are able to pass the imaging ID and patient ID to open something up. Would be glad to discuss more - sidharth/poorna [at] medblocks [dot] com.
Do you have error trapping for biologically implausible values (BIVs)? For example in your forms, does the field have logic associated with the entry to question the user whether they made a mistake in inputing the value? eg. Systolic of 1400, Interocular pressure of 200, etc.?
When you develop these forms in your UI, are they based on a UI definition language that is then parsed and a GUI created on the fly? Or is it just a series of components in a certain UI system (react, vue, etc) that a programmer must stitch together?
@@shofiqulislamrasel9973 and it does! We have a fully functional FHIR API. Just prefer to use openEHR for storing clinical data. This is reflected back in the FHIR API if FHIRConnect mappings are available.
What we need is software that works for people on the ground. And not people changing their workflows to fit within their EHR. We need EHRs that serve the care delivery models and patients well. Today's EHRs don't do that. So to answer your question: We don't need just "another EHR". We need "an EHR per practitioner need", and "an EHR per patient need". Not just 1 more EHR - we need 1000s. It's not impractical to build and maintain these around health data platforms.
![Seungmin "그렇게, 천천히, 우리(As we are)" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/kAzmhLHePqU/mqdefault.jpg)
The App related to Eye Diagnosis is just awesome. You spoke and it got documented, really nice.
Yes! It's a pretty neat demo!
Thank you for sharing your progress with this project! I've worked in Epic and Cerner my entire career, but not in a programming capacity. I set up the billing tables and revenue workflows, then troubleshoot charges. But it's still so fascinating to see how these programs can be built from the ground up!
It's definitely not easy to build it from the ground up. But it enables us to do sooo much!
Great Poorna. I can see you all have made great strides. All the best.❤
He really has!
Great Work Sidharth, Dr. Poornachandra and Medblocks Team 💪🏾 You are definitely attacking the pain points of the monoliths. Being able to customize data collection to your work flow and making that data actionable is a huge win👏
You too Keisha! A lot of fundamental work before we can get there! Glad to be working on the same problem as you!
I'm a med student currently pursuing my internship and I have always thought EHR is going to be a big thing in the future. Especially a modular and DIY kind of EHR could help so many clinicians in both small setups and large hospitals. It could even fuel a new revolution in medical research bringing unexpected correlations between health interventions and outcomes. This has so much untapped potential. Feels really great to see someone making innovation in the field. All the best guys. I hope I can work for you someday.
Best of luck with your internship! I completely agree - there's just so much untapped potential!
Great video! I am curious to know if the speech to complaint documenting feature run locally
It can run on your private cloud. Not yet tested on edge machines.
Hi Sidharth/Poorna, this is a good start. I have some feedback that will be too much to type. Please leave me a message or you have my co-ordinates, if you want to reach out. But in general I would like to ask are you going to restrict this to BCVA/refraction/prescription glasses for ophthalmology ? Sounds like no, with the use of SNOMED-CT as in the demo. I don't see a viewer in this. OCT, FAF, CFP, MP and others are too important if you would like to make it more robust. Most of this is proprietary and not DICOM, although some of them can be DICOM extracted. Right now there are a combination of solutions being worked out. Would be interesting to discuss further
Hey Venu, we have integrated most of the imaging through a SMART app given the patient ID. For eg. we use EIDON (non-mydriatic cams) for every patient, and this is just another iFrame within the patient context. We are yet to strongly link DICOM and structured data capture, but a lot of DICOM viewers do support "context based launch" - where you are able to pass the imaging ID and patient ID to open something up. Would be glad to discuss more - sidharth/poorna [at] medblocks [dot] com.
Do you have error trapping for biologically implausible values (BIVs)? For example in your forms, does the field have logic associated with the entry to question the user whether they made a mistake in inputing the value? eg. Systolic of 1400, Interocular pressure of 200, etc.?
@@smudoshi yes. All our validation is based on openEHR archetypes. Which account for BIVs.
@@medblocks Excellent. Good to hear of your forward thinking, standards based and extensible approach. Wishing you godspeed and great success.
When you develop these forms in your UI, are they based on a UI definition language that is then parsed and a GUI created on the fly? Or is it just a series of components in a certain UI system (react, vue, etc) that a programmer must stitch together?
It’s based on web components. You can build it in any framework and export it!
I had hoped that this project would have some flavor of FHIR.
@@shofiqulislamrasel9973 and it does! We have a fully functional FHIR API. Just prefer to use openEHR for storing clinical data. This is reflected back in the FHIR API if FHIRConnect mappings are available.
What do u think currently are the best HIMS softwares in india who have managed to integrate FIHR, ABDM, SONOMED, LOINC successfully.
Do we need another EHR.. lol
What we need is software that works for people on the ground. And not people changing their workflows to fit within their EHR. We need EHRs that serve the care delivery models and patients well. Today's EHRs don't do that. So to answer your question: We don't need just "another EHR". We need "an EHR per practitioner need", and "an EHR per patient need". Not just 1 more EHR - we need 1000s. It's not impractical to build and maintain these around health data platforms.
@@medblocks, 👏👏👏Which is 100% what you have to do with the monoliths
Do you want to master openEHR? Come join me in my upcoming webinar. Register here now! link.medblocks.com/openehr-workshop-9e1d0d