In my experience, there's no such thing. HL7 is a spec in only the loosest sense of the word. Half the time you had an 80-character console output dumped into the "freetext" fields. Then there's all the codes used for different drugs, tests, admission/discharge (plus differentiating when they're standardized or user-entered with appropriate typos).
Point is, all the costs were really in the integration. Getting access to the HL7 streams wasn't bad once you got far enough in the sales cycle. Once you had it, it was a one-off project to parse the specifics of the messages. And that was just for a read-only analytics system... trying to generate compatible messages to feed back to the EHR is a whole other beast.
That's the challenge getting into this space if you're a web or cloud engineer... you come in with the mindset that "oh, HL7 is a messaging standard, I'll just read the spec and use it." In practice, there's an infinite amount of variability. You really need to treat each hospital as it's own one-off integration, plus all the politics needed to get access to the messages in the first place.
That's exactly why I'd want to tie a nationwide EHR/EMR system to Medicare reimbursements. In this case, not only must you drag the horse to water, you must force it to drink.
In my experience, there's no such thing. HL7 is a spec in only the loosest sense of the word. Half the time you had an 80-character console output dumped into the "freetext" fields. Then there's all the codes used for different drugs, tests, admission/discharge (plus differentiating when they're standardized or user-entered with appropriate typos).
Point is, all the costs were really in the integration. Getting access to the HL7 streams wasn't bad once you got far enough in the sales cycle. Once you had it, it was a one-off project to parse the specifics of the messages. And that was just for a read-only analytics system... trying to generate compatible messages to feed back to the EHR is a whole other beast.
That's the challenge getting into this space if you're a web or cloud engineer... you come in with the mindset that "oh, HL7 is a messaging standard, I'll just read the spec and use it." In practice, there's an infinite amount of variability. You really need to treat each hospital as it's own one-off integration, plus all the politics needed to get access to the messages in the first place.