Home Applications BulkProfile_HL7RoutingRules

BulkProfile_HL7RoutingRules

This application is not supported by InterSystems Corporation. Please be notified that you use it at your own risk.
3
2 reviews
0
Awards
204
Views
0
IPM installs
0
0
Details
Releases
Reviews  (2)
Issues
Pull requests  (1)
IRIS Integration - Bulk find HL7 Routing changes. No UnitTests.

What's new in this version

Publish to IMP / ZPM repo
Changed root package name to mitigate conflict.

BulkProfile_HL7RoutingRules

IRIS Integration utility to report difference in Routing HL7 behaviour between Systems and versions.

Implementation consists of the single class: alwo.UnitTest.RuleSet.BulkProfile

Requirement

  • Facilitate bulk profiling of HL7 message routing on existing production WITHOUT having to swap existing Services for FileService equivalents.
  • Avoid manually writing UnitTests
  • Apply current production message schema behavior

How it works

On System A

  • Read a directory containing HL7 files
  • Individually play them through an existing HL7 production
  • Output a CSV file for routing events

On System B

  • Read a directory containing same HL7 files
  • Individually play them through an existing HL7 production
  • Output a CSV file for routing events

Using faviorite comprison tool:

  • Compare the two CSV files

Comparison of Report files

Install

IPM (ZPM) : install alwo-unittest-ruleset-bulkprofile

How to run utility

set inputDirectory="C:\temp\RuleSetHL7"
set fileWildCard="*.txt"
set outputReport="RuleReportIRIS2022.csv"
set serviceName="From_SystemZ"
set targetName="MsgRouter"
do ##class(alwo.UnitTest.RuleSet.BulkProfile).EvaluateRecords(inputDirectory,fileWildCard,outputReport,serviceName,targetName)

Argument “fileWildCard”

  • A pattern to match HL7 file names to be processed.
  • For example if files have a “.hl7” suffix. Use “.hl7” instead.

Argument “serviceName” (Required)

  • This is the configuration name in the current production for the Service you want to send all HL7 messages from.

Argument “targetName” - (Optional)

  • This is the first target of the service.
  • If not specified will just use the TargetConfigName defined in the current production settings.

By default CSV reports will be created in same directory as source HL7 input files. Specify an absolute path if you want in a different location.

Tested on releases

  • IRIS 4 Health - RedHat 2018.1.2
  • IRIS 4 Health - RedHat 2022.1
  • IRIS 4 Health - Windows 2022.1
Made with
Install
zpm install alwo-unittest-ruleset-bulkprofile download archive
Version
1.0.108 Jul, 2023
Category
Solutions
Works with
InterSystems IRIS for HealthHealthShare
First published
17 Jul, 2022