3 ms·
So, what's the most common standard for PHR information? I've only heard of HL7 which is basically paying money for a bunch of XSDs (of course)
by raverbashing 11y ago
So, what's the most common standard for PHR information?
I've only heard of HL7 which is basically paying money for a bunch of XSDs (of course)
- methehack 11y agoIf I understand your question, probably a CCDA. I think the real problem is no system has a reliably comprehensive picture. After that, it is challenging to find a reliable global patient identifier. Epic says they have the health records of 175M americans. I would say they have parts of records of 175M americans and probably a lot of dupes.
- cordite 11y agoGiven that these numbers are individually sourced from customers, customers own their own data, and all interchange is P2P--there's not a good way to really count. Customers own their range of member-numbers as well. Plus, the whole thing about identity is even more difficult, you can't go by name, SSN, and DOB alone. As far as I know, HL7 is mostly used between internal systems within an organization. For sending actual patient data, allergies, conditions, CCDA is usually used for communication with non-Epic EMRs belonging to other organizations. As an aside, CCDA and HL7 don't support rich data well, so they usually end up as base64 encoded PDFs.
- cordite 11y agoThere are different versions of HL7. Currently the common one is some line and character delimited format, HL7 v2. {OBX,ORC,etc.} |data|||more data|number|||identifier| Which is basically a member of the multimap with the first word as the key, with an indexed map of text. It's not really a standard like HTML, at least no EMRs, interface systems, instruments, and so on abide by them. So, whenever systems hook up, there has to be setup / build to map what text means what to each other--although the positions are generally agreed upon. When interfacing systems together, there is both a legal and a technical cost that must be dealt with. With highly configurable systems on both ends, figuring out who's terms / categories equate on the other side and back is not an easy task and most organizations hesitate to go through with it unless necessary. The tools are there, it's just that when everyone customizes their own universe, it's unlikely to work out of the box. You can stick a german and a guy from holland together in the same room, they might have some shared words, but whether they can hold a coherent conversation in their native tongue is a different matter.