Clinical messaging
AvailableHL7 v2 Message Creator
A desktop tool for building, editing and sending HL7 v2 test messages. Start from a template or a message you already have, change any field, and send one message or a whole group to the system under test.
How a run works
- 01
Template or message
Pick a type, or paste one in
- 02
Edit and map
Segment by segment, field by field
- 03
Send over MLLP
One message, or a group in order
- 04
Acknowledgement
The reply to each, as it arrives
What it does
Building messages
- Templates for common message types: ADT for registration and updates, ORM orders, ORU results, SIU scheduling and MDM documents.
- An editor that works segment by segment and field by field, with field names shown beside the values.
- Paste an existing message to load it, then change what you need.
- Map values from an existing message onto a template, so test data follows the shape of the real feed.
Sending
- Send over MLLP to any host and port you define, such as a RIS receiving orders.
- Targets saved and named, so a test environment is picked rather than typed.
- Send messages in groups, in the order you set.
Checking
- The acknowledgement for every message: accepted, error or rejected, with the error detail.
- A log of what was sent and what came back.
At a glance
- Runs on
- A desktop workstation. Tell us your operating system and we will confirm the build.
- Speaks
- HL7 v2.x over MLLP
- Message types
- ADT, ORM, ORU, SIU, MDM
- Data
- Messages stay on your machine and your network.
- Access
- By request. We send a download link and its terms of use.
Point it at test systems
A message sent to a production interface becomes part of a real record. Use test targets, and check the processing ID before sending to anything shared.
Coming next
What we are adding, roughly in order. Tell us in your request which of these matters to you, and it moves up.
- 01Scenarios rather than single messages: register a patient, place an order, return a result, with identifiers and accession numbers carried from step to step.
- 02Validation against conformance profiles, including IHE Radiology Scheduled Workflow, IHE PAM and PIX/PDQ, and the CDC ELR 2.5.1 guide.
- 03OML and OMI order messages alongside ORM.
- 04Expected acknowledgements per step, so a group of messages becomes a test that passes or fails.
- 05A listener, to capture what the target sends back or forwards.
- 06Bulk messages from a spreadsheet and a mapping.
- 07Test processing ID (MSH-11 = T) by default, with a warning before sending to a target not marked as test.
Questions
HL7 v2.x. Tell us the version and any implementation guide your interface follows in the request, and we will say how well the current templates fit it.
Yes. Any segment can be edited as text, so local segments are kept when you load a message and sent as you wrote them.
No. It works with HL7 v2. A FHIR front end for v2-only systems is one of the tools in development.
Ask us. Access terms are sent with the download link, and they depend on how you plan to use it.
Request information
Tell us what you are working on and what you would like to know. If the tool is a fit, the reply includes a download link.
