Automate time-consuming HL7 spec creation and gap analysis. Create HL7 conformance statements that simplify interface requirements-gathering. Eliminate mind-numbing, repetitive manual work. Take control of the system specifications, customizations and coding requirements.
Gap analysis is critical to HL7 scoping. Understand the difference between the source and destination systems at the messaging level and know exactly what it is you need to configure. Identify the gaps in hours, not days.
The Gap Analysis Workbench makes it all happen. Compare message types, segments, fields, and data. Save anytime and pick up where you left off.
Once your gap analysis is pinned down, you’ll have comprehensive documentation of project tasks. Conformance allows you to export those results to an Excel worksheet. Share that Excel worksheet with your interface configuration team.
Focus on the gaps that matter to you for HL7 scoping. Select the specific criteria and elements that you need analyzed among the messages, segments, fields and data tables between the 2 profiles being compared.
It’s not enough to understand just what data is different. You need to know the difference in how that data is formatted. Conformance analyzes both format and content gaps for effective interfacing.
There is variance in how code sets identify data. For example, PID-8 Administrative Sex in HL7 v2.6 specifies 6 different possible values. Even then, a vendor or provider might choose different values and still be HL7 compliant. The interface needs to map those values. The Gap Analysis Workbench lets you automate this work.
Learn how Interface Lifecycle Management can cut complexity and costs.
Hello HL7 community, we’ve decided to give the old HL7-Definition reference website its well-deserved retirement. We’re now proud to introduce the new and improved HL7-Definition V2 website.
We’ve been asking for [...]HL7-Definition V2