Versions Compared

Old Version 2

changes.mady.by.user Lianne So

Saved on

compared with

New Version 3

changes.mady.by.user Aryn Wiebe

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
titleSTEP 2: Localize the mappings and filters folders to the component

Drag and drop the HL7MAP/mappings and HL7MAP/filters folders outside of the HL7MAP library into the component’s Project Tree. This will allow you to customize filtering and mapping logic for a specific integration.

When initializing the HL7MAP object with custom mappings and filters directories, use the following syntax:

Code Block
local H = HL7MAPclient{filter_dir="NEW_FILTER_LOCATION",mapping_dir="NEW_MAPPING_LOCATION""}
Expand
titleSTEP 3: Update In the mappings folder, update HL7codemaps

Update mappings/HL7MAPcodemaps to the specific codesets and HL7 versions your messages will be using.

Expand
titleSTEP 4: Update/add filtering modules

Update or add message-specific filter modules in the HL7MAP/filters folder. The modules should be named [HL7_Type].lua.

Messages with an inbound HL7 message type (ex. ADTA01) that matches the name of a filtering module (ex. ADTA01.lua) will be filtered by that module. All other messages will be filtered by the default filter conditions in HL7MAP/filters/default.lua, which can also be further customized.

Expand
titleSTEP 5: Update/add mapping modules

Update or add mapping modules in the HL7MAP/mappings folder. The modules should be named [HL7_Type].lua.

By default, only messages with an outbound HL7 message type (ex. ADTA01) that matches the name of a mapping module (ex. ADTA01.lua) will be mapped. All other messages will be pushed downstream in their original form.