Stream: V2
Topic: v2 tools
René Spronk (Oct 12 2020 at 15:06):
In our v2 training courses, we use a v2 editor/validator for our exercises.
We tend to use 7Edit on Windows (we're also considering HL7Soup), what would you recommend we use for Mac ? HL7 Inspector works, but the GUI is not that nice, HL7 Testpanel (HAPI) uses a Java version that's too old for the Mac. Any alternatives for the Mac ? (yes, a virtual machine with 7Edit works, but we'd like to use a native tool, also for Linux)
Rob Snelick (Oct 12 2020 at 16:29):
By v2 editor, do you mean message editor or profile editor?
René Spronk (Oct 12 2020 at 17:28):
message editor. If its also a profile editor, then that's a bonus, but primarily we use a "v2 message instance editor & validator"
René Spronk (Oct 13 2020 at 12:01):
@Rob Snelick Has HL7.org now 'officially' embraced the NIST v2 profiling tools instead of MWB ?
Rob Snelick (Oct 13 2020 at 13:09):
There is a project (PSS) that is still in progress to do so. The goal is have v2 IGs use the tool for balloting; this ensures certain quality and conformance measures built in (computable requirements). This does not preclude other tools that meet HL7 v2 conformance methods.
Rob Snelick (Oct 13 2020 at 13:23):
The NIST v2 tools (https://hl7v2tools.nist.gov) has tools for profiling (creating IGs containing one or more message profile--both the narrative and structure), creating test cases (including the ability to create and edit messages) and message validation. Once a profile is built using the platform, a validation tool is automatically built. The tool set is publicly available via web apps (browsers) so they are OS independent. The validation tools are used in the US for meaningful use certification and other testing programs. The tools follow the profiling methods described in the recently published v2 conformance methodology--this specification removed the conformance chapter from the based v2 standard, it is now a standalone specification and applies to all versions of v2.
René Spronk (Oct 13 2020 at 14:35):
See https://vimeo.com/467764562, a small e-learning video which is part of our HL7 v2 training course. Validators and editor/validators are used by most v2 implementers, IMHO v2 profiling tools are only of use to a small portion of implementers.
Rinold S (Oct 15 2020 at 08:35):
Hey :)
I'm trying to validate HL7 using clinical Package Validator. I'm using VS code editor for to write the sample message. After saving the message text with .hl7 ext. I get an error: message contains a non-ASCII character
at position 259.
my VScode encoding is UTF-8 default. what to do to put off this error?
Rinold S (Oct 15 2020 at 08:54):
It should deal with the editor. Any hl7 editor is available ?
René Spronk (Oct 15 2020 at 09:14):
I had to google: this is a Australian government validator, as far as I can see for HL7 CDA (and not for v2). You'd best ask the authors of that tool if you have any issues with it.
Rinold S (Oct 16 2020 at 07:21):
@René Spronk I sorted the issues by encoding the file to US-ASCII .
Rinold S (Oct 16 2020 at 07:23):
I downloaded 7Edit professional and used that editor to generate a new hl7 message in US-ASCII encode.
The editor is bit slow.
Could anyone suggest any good hl7 editor please.
René Spronk (Oct 16 2020 at 08:11):
IMHO 7Edit is currently the best commercial offering. If you watch the video mentioned above you'll see the names of some of the other popular ones. Hl7 v2 is an old standard, so some of the v2 tools are no longer supported, which means the list of options (esp. open source solutions) is dwindling.
Rinold S (Oct 16 2020 at 08:15):
Thank you @René Spronk .
Last updated: Apr 12 2022 at 19:14 UTC
