4 ms·
> a large amount of what we were after as researchers was only available in free-text Is there no way to parse this? Surely the EMR systems could have a simple
by matheusmoreira 5y ago
> a large amount of what we were after as researchers was only available in free-text
Is there no way to parse this? Surely the EMR systems could have a simple key-value syntax. Patient history is too complex to be expressed that way but there is a lot of other valuable data that could. Blood pressure, for example. Ideally, things like lab results would already be stored as structured data.
- drknownuffin 5y agoWith existing tech? No, not really. Most of those lab values are more or less worthless outside of context - which is why so much time is spent on training docs on physio, pathophys, and history taking. I know that it's frustrating to hear, but it's why every "helpful" tech solution to date has resulted in increasing doc griping and burnout.
- matheusmoreira 5y agoEven simple charts for numerical variables would be helpful though. For example, evaluating growth over time is important in pediatrics. In my country, mothers receive a booklet with all the charts and pediatricians are supposed to fill it with data during consults. When I open one of these, I usually find only two or three data points. Surely EMR software could do the same thing automatically. https://www.cdc.gov/growthcharts/index.htm https://www.cdc.gov/growthcharts/index.htm
- drknownuffin 5y agoIn the US, growth charts for peds are already built into every EMR I know of. But even that isn't particularly nuanced: I want different charts at different ages based on, for instance, whether the kid is bottle or breast-fed. The difference will impact an interpretation of being under- or over-weight, and using the wrong ones can create the appearance that the kid is dropping off the growth curve at around two years old (which is to say, without context you can't even interpret just the trend itself). The EMRs aren't even at the "IF feeding==bottle, display.curveA; ELSE display.curveB" level of sophistication. Which is another way of saying "even where it looks like the numbers matter unto themselves without context, nope, you still can't meaningfully interpret them without context."
- potatoman22 5y agoCertain EMRs have lab data and diagnostics stored like this. That data is used in ML algorithms. That data lies outside of free-text.
- Spivak 5y agoI mean they kinda do since lots and lots of systems support HL7 which can best be described as "JSON but so so so much worse" or "CSV with '|' kinda."
- creyes 5y ago"Lots of systems" is a stretch, only a few do. In fact, "support" is a stretch. Most EMRs (Cerner, Epic etc) only support HL7 as much as it gets them their CMMI / Promoting Interoperability certifications which are not relevant for actual use. That being said, it is JSON but much worse
- joshuakelly 5y agoThis is a bit of a simplification. HL7 is the standards body, not the standard itself - which (for everyone else who may not know) is "HL7 v2". FHIR is an actually-JSON (+XML) health data protocol that is gaining adoption (most recently because of CMS Interoperability and Patient Access Final Rule), so it's not all bad.
- Spivak 5y agoFHIR is a breath of fresh air but it's so kinda worse because while it's great you still need the HL7 parser logic lying around in your code and now a bunch of additional code paths for FHIR :/
- BadInformatics 5y agoPrior to FHIR, there was actually an XML-based HL7 v3 as well. Mercifully, it collapsed under the weight of its own spec and rarely shows up in the wild these days. CDA still survives, but it's much easier to work with and being slowly made obsolete by FHIR resources.
- joshuakelly 5y agoI'm working on dev tools in this space. Care to exchange notes with me? Email is in profile.