3 ms·
Show HN: MLonFHIR: Fusing Sklearn with the HL7 FHIR Standard
- aliljet 7y agoThis is an excellent idea. From unfortunate experience, I know this will struggle to be real in a hospital that's suffering with Epic. The company is strictly against open standards (https://www.cnbc.com/amp/2020/01/22/epic-ceo-sends-letter-urging-hospitals-to-oppose-hhs-data-sharing-rule.html https://www.cnbc.com/amp/2020/01/22/epic-ceo-sends-letter-ur...). The Epic scam continues unabated, but I wonder if there's a way to add more explicit rejections (or constraints) for Epic environments?
- coolyd 7y agoThey do support a fair number of FHIR resources (as required by meaningful use stage 3): https://open.epic.com/Interface/FHIR https://open.epic.com/Interface/FHIR and even more within their curated marketplace: https://apporchard.epic.com/ https://apporchard.epic.com/
- ebg13 7y ago"the HL7 FHIR standard" Which one? R4? STU3? -> http://hl7.org/fhir/directory.html http://hl7.org/fhir/directory.html AFAIK, the different versions aren't compatible with each other. How will that affect this library?
- cbock90 7y agoGood point. As of now, we only tested it with STU3. I think something we definitely miss is a test module that allows for version compatibility checks.
- ebg13 7y agoI'll be watching this project. I hope you can keep advancing it. Maybe put a note on the README about version compatibility and a call to action for testing new versions as they come out?