Integrations & data · Practice guide

Check the meaning of information exchanged through HL7

Illustrative situation

HL7 refers to standards used to exchange healthcare information between systems. An interface transfers a value that has a different local meaning in the receiving system. The same code or label can mean different things in different organisations. Transferring it without agreement can create a record that looks valid but is misunderstood. Have the responsible teams review the meaning of important fields.

Healthcare booking calendars on two connected screens with blue and orange appointment cards.
Make the handover between tools clear for the team using them.

What this means for your practice

Ask suppliers to explain field meanings, local codes and assumptions for the responsible teams to review. A message can be accepted by software while still giving staff the wrong understanding.

An example to discuss with your team

Use a fictional uncommon code and inspect the receiving interpretation.

Healthcare data integration connecting two applications through a field-mapping board.
Agree what each field means and which system owns it.
Healthcare data validation separating matched records from an exception tray.
Make rejected or uncertain records visible for review.

Questions to take to your supplier

Send a fictional uncommon code and inspect its interpretation at the destination. Ask what happens when no agreed mapping exists. A visible review item is preferable to an unexplained default. Keep responsibility for meaning with the people who understand the service, supported by the suppliers implementing it.

Agree the working process

Identify the fields whose meaning affects what the receiving team does next. Local service codes, locations or status labels may require explanation even when their format is straightforward. Give each important mapping a business owner who can confirm the interpretation, supported by the suppliers implementing it. Use a short set of fictional examples, including an uncommon value and one with no agreed match. Ask what the system does when the mapping is missing: a default should not silently invent meaning.

Keep unresolved cases in a visible review route and record how approved corrections are applied. Test the receiving screen with staff, because a transfer accepted by software may still be misleading to its users. Review mappings when either organisation changes its local options. The work is not finished once a spreadsheet of codes exists; the value comes from consistent interpretation in the actual workflow and a maintained process for questions that arise later.

How to check the result

Count mappings requiring manual correction after transfer.

Turn reading into a next step

Your action checklist

Work through these checks with your team or supplier. Tick the ones you have resolved and leave unknowns open.

Checks to discuss

Record what you know, what is still missing and the answer you need from your team or supplier.

Use project decisions only, without personal, patient or confidential details. Entries stay in this page and are not submitted to Kay & Co. Copy or download before leaving; this page does not save your notes.

Further reading

These sources provide background for the topic. The practice examples and checklist are illustrative planning suggestions from Kay & Co.

Related guides

Need help with this?

Tell us what is getting in the way. Kay & Co. can help you understand the options and turn the next step into something that works for your practice.

Explore integrations & data services or discuss your project.

Try the free Healthcare Digital Planner to find your starting priority.