robholme/hl7-powershell-module

HL7 PowerShell Module

Project Description

This PowerShell module is a small collection of CmdLets to manipulate HL7 v2.x files, including:

• Select-HL7Item: queries a HL7 file (or list of files) to return a specific HL7 Item.
• Set-HL7Item: changes the value of an existing item within a HL7 file
• Remove-HL7Item: delete the value for a nominated item in the HL7 message.
• Send-HL7Messsage: send a HL7 file to a remote host via TCP.
• Remove-HL7Identifiers: remove personal identifiers for patients and next of kin from HL7 files.
• Split-HL7BatchFile: Split a batch file containing multiple messages into a separate file per message.
• Receive-HL7Message: Receive a HL7 v2.x message via a TCP connection
• Show-HL7MessageTimeline: List messages chronologically based on the header timestamp (MSH-7)

Installation Instructions

You may install the module from existing build releases, from the Powershell Gallery, or build from source.

Install from Powershell Gallery

From a powershell console, run:

Install-Module -Name hl7tools

Install from GitHub releases

Follow these instructions if you plan on installing the module from a prebuilt release instead of building from source.

1. Download the zip file from the latest release from: https://github.com/RobHolme/HL7-Powershell-Module/releases.
2. Extract the 'hl7tools' folder from the archive to your PowerShell modules folder. You can confirm the location of your modules folder by running $env:PSModulePath from a PowerShell console.
3. Run the PowerShell command Unblock-File against all files extracted from the download.
4. Open a powershell console, the module will be imported when the console opens and the CmdLets available to use. Alternatively, if you don't wish to load the module with all new powershell sessions, run import-module .\hl7tools\hl7tools.psd1 to use the module for the current session only.

Build from source

The solution will build versions for .Net 6.0 (Microsoft Powershell 6+) and .Net Framework 4.52 (Windows Powershell 5.1). The powershell module will load the relevant dll based on the Powershell environment it is run from. If you only wish to target .Net standard or .Net Framework alone, the .csproj file will need to be edited accordingly to specify a single TargetFramework.

1. Install the .Net 6 SDK and the .Net Framework 4.5.2 SDK. Install instructions for the SDK for each platform are available from:

• Linux: https://docs.microsoft.com/en-us/dotnet/core/linux-prerequisites?tabs=netcore2x
• Windows: https://docs.microsoft.com/en-us/dotnet/core/windows-prerequisites?tabs=netcore2x
• MacOS: https://docs.microsoft.com/en-us/dotnet/core/macos-prerequisites?tabs=netcore2x

1. Open a command console, navigate to the root folder of this solution (containing hl7tools.csproj). Run the following commands to build the release and publish to the /module/lib folder:

dotnet publish --configuration release --framework net6.0 --output .\module\hl7tools\lib\net6.0\

dotnet publish --configuration release --framework net48 --output .\module\hl7tools\lib\net48\

(or run the .\publish.cmd batch file)

2. The build process will copy each version of hl7tools.dll to subfolders of module\hl7tools\lib\. The contents of the \module\hl7tools folder will contain the Powershell Module.
3. Move the \hl7tools folder to your Powershell Module Path (query the path from the environment variable by running $env:PSModulePath from a powershell console). Restart powershell. Alternatively, if you don't wish to load the module with all new powershell sessions, run import-module .\hl7tools\hl7tools.psd1 to use the module for the current session only.

CmdLet Usage

Select-HL7Item

This CmdLet returns the values of specific HL7 items from a file (or group of files). This is intended to aid with integration work to validate the values of fields over a large sample of HL7 messages. Some basic filtering is available to only include specific messages from a larger sample.

Output can be piped to other powershell CmdLets to refine the results. e.g. returning only the unique values across a range of files:

Select-HL7Item [-LiteralPath] <string[]> [-ItemPosition] <string[]> [-Filter <string[]>] [[-Encoding] <String>] [<CommonParameters>]

Select-HL7Item [-Path] <string[]> [-ItemPosition] <string[]> [-Filter <string[]>] [[-Encoding] <String>] [<CommonParameters>]

Example:

• Select-HL7Item -Path c:\test -ItemPosition PID-3.1 Display the Patient ID values for all hl7 files in c:\test
• get-childitem *.hl7 | Select-HL7Item -ItemPosition PID-3.1 Pipe all files with .hl7 extentions to the CmdLet, return Patient ID values
• Select-HL7Item -Path c:\test -ItemPosition PID-5 -Filter PV1-2=INPATIENT Display all PID-5 values where the value of PV1-2 is INPATIENT
• (Select-HL7Item -Path c:\test -ItemPosition PID-3.1).ItemValue | Sort-Object -Unique Only return unique values
• Select-HL7Item -Path c:\test\*.hl7 -ItemPosition PID-3.1,PID-5 Display the Patient ID and Patient Name values for all hl7 files in c:\test

Parameters

-Path <string[]>: The full or relative path a single HL7 file or directory. This may include wildcards in the path name. If a directory is provide, all files within the directory will be examined. Exceptions will be raised if a file isn't identified as a HL7 v2.x file. This parameter accepts a list of files, separate each file file with a ','

-LiteralPath <string[]>: Same as -Path, only wildcards are not expanded. Use this if the literal path includes a wildcard character you do not intent to expand.

-ItemPosition <string[]>: A string, or list of strings, identifying the location of the item(s) in the HL7 message you wish to retrieve the value for.

ItemPosition Examples:

• -ItemPosition PID All PID segments
• -ItemPosition PID-3 The value for the 3rd PID field. If this item is a list all PID-3 values in the list will be returned.
• -ItemPosition PID-3[1] The value of the 3rd PID field, but for only the first occurrence of PID-3 (assuming PID-3 is a list)
• -ItemPosition PID-3.1 The value for the 1st component of the PID-3 field. If the component belongs to a list of fields, all PID-3.1 components will be returned.
• -ItemPosition PID-3[2].1 The value for the 1st component of the second occurrence of the PID-3 field (assuming the field is a list).
• -ItemPosition PID-3.1.1 The value for the first sub-component of the first component of the 3rd field of the PID segment.
• -ItemPosition PID-3.1,PID-5 The value for the 1st component of the PID-3 field, and the value of the PID-5 field.

-Filter <string[]>: Only includes messages where a HL7 item equals a specific value. The format is: HL7Item=value. The HL7Item part of the filter is of the same format as the -ItemPosition parameter. The -Filter parameter accepts a list of filters (separated by a comma). If a list of filters is provided then a message must match all conditions to be included.

If a filter references a repeating element, then a match is returned as successful if any of the repeats match the condition. A position within the repeating element can be nominated if the order is known.

The filter is intended to filter at the message/file level when querying a large number of files (to include/exclude the messages from the results). It will not filter on individual repeating segments or fields within a message - the results will still include all fields requested from the messages matched by the filter condition. e.g. if you filter on OBX-3=NM, all OBX-3 values from all OBX segments will be returned, but only for messages queried that contain at least 1 OBX-3 value equal to 'NM'. Message not matching the filter condition are excluded from the results.

Filter Examples:

• -Filter MSH-9=ADT^A05 This filter would only include messages that had "ADT^A05" as the value for the MSH-9 field.
• -Filter MSH-9=ADT^A05,PV1-2=OUTPATIENT This filter would only include messages where both the MSH-9 field contained "ADT^A04" and the PV1-2 field contained "OUTPATIENT"
• -Filter PID-3[2].1=Z9999 This filter would only include messages with the second repeat of the PID-3 fields matching 'Z9999'

-Encoding <string>: Specify the character encoding. Supports "UTF-8" or "ISO-8859-1" (Western European). Defaults to "UTF-8" if parameter not supplied.

Note: Items that cannot be located in the message will display a warning. To suppress the warning messages use the -WarningAction Ignore common parameter.

Send-HL7Message

Send a HL7 v2.x message from a file (or list of files) via TCP to a remote endpoint. Messages are framed using MLLP (Minimal Lower Layer Protocol).

Send-HL7Message [-HostName] <string> [-Port] <int> [-LiteralPath] <string[]> [-NoACK] [-Delay] <int> [[-Encoding] <String>] [-UseTLS] [-SkipCertificateCheck] [<CommonParameters>]

Send-HL7Message [-HostName] <string> [-Port] <int> [-Path] <string[]> [-NoACK] [-Delay] <int> [[-Encoding] <String>] [-UseTLS] [-SkipCertificateCheck] [<CommonParameters>]

example:

Send-Hl7Message -Hostname 192.168.0.10 -Port 1234 -Path c:\HL7Files\message1.hl7

Send-Hl7Message -Hostname 192.168.0.10 -Port 1234 -Path c:\HL7Files\*.hl7 -Encoding ISO-8859-1

Send-Hl7Message -Hostname secure-hl7.company.com -Port 5000 -Path c:\HL7Files\*.hl7 -Encoding UTF-8 -UseTLS

Parameters

-Hostname <string>: The IP Address or host name of the remote host to send the HL7 message to

-Port <int>: The TCP port of the listener on the remote host to send the HL7 message to.

-Path <string[]>: The full or relative path a single HL7 file or directory. This may include wildcards in the path name. If a directory is provide, all files within the directory will be examined. Exceptions will be raised if a file isn't identified as a HL7 v2.x file. This parameter accepts a list of files, separate each file file with a ',' (no spaces).

-LiteralPath <string[]>: Same as -Path, only wildcards are not expanded. Use this if the literal path includes a wildcard character you do not intent to expand.

-NoACK: This switch instructs the CmdLet not to wait for an ACK response from the remote host.

-Delay <int>: The delay (in seconds) between sending each message.

-Encoding <string>: Specify the character encoding used when sending the message. Supports "UTF-8" or "ISO-8859-1" (Western European). Defaults to "UTF-8" if parameter not supplied.

-UseTLS: Secure the connection to the remote host via TLS. Requires the remote host to support TLS. Experimental, not widely tested.

-SkipCertificateCheck: Ignore TLS certificate validation errors (trust, validity, etc). Used in conjunction with -UseTLS switch, has not impact otherwise.

Remove-HL7Identifiers

Removes names, addresses and other personally identifiable details from a HL7 v2.x Message.

Note: Identifier codes in {"PID-3"} remain. This masks the following fields from a HL7 v2.x file:

• All PID fields except {"PID-1, PID-2, PID-3"}
• All NK1 fields except {"NK1-1, NK1-3"}
• All IN1 fields
• All IN2 fields

By default a new file is saved in the same location as the original file with "MASKED_" prefixed to the file name. If the optional "-OverwriteFile" switch is set the original file will be modified.

Remove-HL7Identifiers [-LiteralPath] <string[]> [[-CustomItemsList] <string[]>] [[-MaskChar] <char>] [[-OverwriteFile]] [[-Encoding] <String>] [-WhatIf] [-Confirm] [<CommonParameters>]

Remove-HL7Identifiers [-Path] <string[]> [[-CustomItemsList] <string[]>] [[-MaskChar] <char>] [[-OverwriteFile]] [[-Encoding] <String>] [-WhatIf] [-Confirm] [<CommonParameters>]

examples:

Remove-HL7Identifiers -Path c:\hl7files\*.hl7 -OverwriteFile

Remove-Hl7Identifiers -Path c:\test.txt

Remove-HL7Identifiers -Path c:\test\testfile.hl7 -CustomItemsList PID-3.1,NK1,DG1

Parameters

-Path <string[]>: The full or relative path a single HL7 file or directory, or a list of files. This may include wildcards in the path name. If a directory is provide, all files within the directory will be examined. Exceptions will be raised if a file isn't identified as a HL7 v2.x file. This parameter accepts a list of files, separate each file file with a ','

-LiteralPath <string[]>: Same as -Path, only wildcards are not expanded. Use this if the literal path includes a wildcard character you do not intent to expand.

-CustomItemsList <string[]>: A list of the HL7 items to mask instead of the default segments and fields. List each item in a comma separated list (no spaces). Items can include a mix of segments (e.g. PV1), Fields (e.g. PID-3), Components (e.g. {"PID-3.1"}) or Subcomponents (e.g. {"PV1-42.2.2"}). For repeating segments and fields a specific repeat can be identified (index starts at 1). e.g. {"PID-3[1].1"} will mask out the first occurrence of {"PID-3.1"}, leaving other repeats of {"PID-3.1"} unchanged. Likewise {"IN1[2]"} will mask out the second occurrence of the IN1 segments only.

CustomItemsList Examples:

• -CustomItemsList PID-3.1,PID-5,PID-13,NK1

-MaskChar <char>: The character used to mask the identifier fields, Defaults to '*' if not supplied

-OverwriteFile: If this switch is set, the original file is modified.

-Encoding <string>: Specify the character encoding. Supports "UTF-8" or "ISO-8859-1" (Western European). Defaults to "UTF-8" if parameter not supplied.

Set-HL7Item

This CmdLet changes the value of an existing HL7 item from a file (or group of files). Some basic filtering is available to only include specific messages within a large sample. By default only the first occurrence of an item will be changed unless the -UpdateAllRepeats switch is set.

Set-HL7Item [-LiteralPath] <string[]> [-ItemPosition] <string> [-Value] <string> [-Filter <string[]>]  [-UpdateAllRepeats] [-AppendToExistingValue] [[-Encoding] <String>] [-WhatIf] [-Confirm] [<CommonParameters>]

Set-HL7Item [-Path] <string[]> [-ItemPosition] <string> [-Value] <string> [-Filter <string[]>]  [-UpdateAllRepeats] [-AppendToExistingValue] [[-Encoding] <String>] [-WhatIf] [-Confirm] [<CommonParameters>]

examples:

Set-HL7Item -Path c:\hl7files\hl7file.txt -ItemPosition PID-3.1 -Value A1234567

Set-HL7Item -Path c:\hl7files\*.hl7 -ItemPosition PV1-3.1 -Value A1234567 -Filter PV1-2=INPATIENT

Parameters

-Path <string[]>: The full or relative path a single HL7 file or directory. This may include wildcards in the path name. If a directory is provide, all files within the directory will be examined. Exceptions will be raised if a file isn't identified as a HL7 v2.x file. This parameter accepts a list of files, separate each file file with a ','

-LiteralPath <string[]>: Same as -Path, only wildcards are not expanded. Use this if the literal path includes a wildcard character you do not intent to expand.

-ItemPosition <string>: A string identifying the location of the item in the HL7 message you wish to retrieve the value for.

ItemPosition Examples

• -ItemPosition PID All PID segments
• -ItemPosition PID-3 The value for the 3rd PID field. If this item is a list all PID-3 values in the list will be returned.
• -ItemPosition PID-3[1] The value of the 3rd PID field, but for only the first occurrence of PID-3 (assuming PID-3 is a list)
• -ItemPosition PID-3.1 The value for the 1st component of the PID-3 field. If the component belongs to a list of fields, all PID-3.1 components will be returned.
• -ItemPosition PID-3[2].1 The value for the 1st component of the second occurrence of the PID-3 field (assuming the field is a list).
• -ItemPosition PID-3.1.1 The value for the first sub-component of the first component of the 3rd field of the PID segment.

-Value <string[]>: The new value to set the item to.

-UpdateAllRepeats: Update all occurrences identified by -ItemPosition

-AppendToExistingValue: The value supplied by the '-Value' parameter is appended to the original value in the message (instead of replacing it).

-Filter <string[]> Only includes messages where a HL7 item equals a specific value. The format is: HL7Item=value. The HL7Item part of the filter is of the same format as the -ItemPosition parameter. The -Filter parameter accepts a list of filters (separated by a comma). If a list of filters is provided then a message must match +all+ conditions to be included.

The filter is intended to filter at the message/file level when querying a large number of files (to include/exclude the messages from the results). It will not filter on individual repeating segments or fields within a message - the results will still include all fields requested from the messages matched by the filter condition. e.g. if you filter on OBX-3=NM, all OBX-3 values from all OBX segments will be returned, but only for messages queried that contain at least 1 OBX-3 value equal to 'NM'. Message not matching the filter condition are excluded from the results.

Filter Examples:

• -Filter MSH-9=ADT^A05 This filter would only include messages that had "ADT^A05" as the value for the MSH-9 field.
• -Filter MSH-9=ADT^A05,PV1-2=OUTPATIENT This filter would only include messages where both the MSH-9 field contained "ADT^A04" and the PV1-2 field contained "OUTPATIENT"

-Encoding <string>: Specify the character encoding. Supports "UTF-8" or "ISO-8859-1" (Western European). Defaults to "UTF-8" if parameter not supplied.

Note: items that cannot be located in the message will display a warning. To suppress the warning messages use the "-WarningAction Ignore" common parameter.

Remove-HL7Item

Deletes the value of specified items from the HL7 message. A list of items, or single item can be specified.

Remove-HL7Item [-LiteralPath] <string[]> [-ItemPosition] <string[]> [[-Filter] <string[]>] [-RemoveAllRepeats] [[-Encoding] <String>] [-WhatIf] [-Confirm] [<CommonParameters>]

Remove-HL7Item [-Path] <string[]> [-ItemPosition] <string[]> [[-Filter] <string[]>] [-RemoveAllRepeats] [[-Encoding] <String>] [-WhatIf] [-Confirm] [<CommonParameters>] 

Parameters

-Path <string[]>: The full or relative path a single HL7 file or directory. This may include wildcards in the path name. If a directory is provide, all files within the directory will be examined. Exceptions will be raised if a file isn't identified as a HL7 v2.x file. This parameter accepts a list of files, separate each file file with a ','

-LiteralPath <string[]>: Same as -Path, only wildcards are not expanded. Use this if the literal path includes a wildcard character you do not intent to expand.

-RemoveAllRepeats: Delete all repeats identified, Defaults to only deleting the first occurrence if this switch is not set.

-ItemPosition <string[]>: A string identifying the location of the item in the HL7 message you wish to delete the value for. Provide a list of items to identify more than one location to delete.

ItemPosition Examples:

• -ItemPosition PID All PID segments
• -ItemPosition PID-3 The 3rd PID field. .
• -ItemPosition PID-3,PID-4,NK1-2 deletes the values for PID-3, PID-4 and NK-2.
• -ItemPosition PID-3[1] The value of the 3rd PID field, but for only the first occurrence of PID-3 (assuming PID-3 is a list)
• -ItemPosition PID-3.1.1 The value for the first sub-component of the first component of the 3rd field of the PID segment.

-Filter <string[]> Only includes messages where a HL7 item equals a specific value. The format is: HL7Item=value. The HL7Item part of the filter is of the same format as the -ItemPosition parameter. The -Filter parameter accepts a list of filters (separated by a comma). If a list of filters is provided then a message must match +all+ conditions to be included.

The filter is intended to filter at the message/file level when querying a large number of files (to include/exclude the messages from the results). It will not filter on individual repeating segments or fields within a message - the results will still include all fields requested from the messages matched by the filter condition. e.g. if you filter on OBX-3=NM, all OBX-3 values from all OBX segments will be returned, but only for messages queried that contain at least 1 OBX-3 value equal to 'NM'. Message not matching the filter condition are excluded from the results.

Filter Examples:

• -Filter MSH-9=ADT^A05 This filter would only include messages that had "ADT^A05" as the value for the MSH-9 field.
• -Filter MSH-9=ADT^A05,PV1-2=OUTPATIENT This filter would only include messages where both the MSH-9 field contained "ADT^A04" and the PV1-2 field contained "OUTPATIENT"

-Encoding <string>: Specify the character encoding. Supports "UTF-8" or "ISO-8859-1" (Western European). Defaults to "UTF-8" if parameter not supplied.

Split-HL7BatchFile

Splits a HL7 batch file into a separate file per HL7 message

Split-HL7BatchFile -LiteralPath <string[]> [-OverwriteFile] [-WhatIf] [<CommonParameters>]

Split-HL7BatchFile [-Path] <string[]> [-OverwriteFile] [-WhatIf] [<CommonParameters>]

Parameters

-Path <string[]>: The full or relative path a single HL7 file or directory. This may include wildcards in the path name. If a directory is provide, all files within the directory will be examined. Exceptions will be raised if a file isn't identified as a HL7 v2.x file. This parameter accepts a list of files, separate each file file with a ','

-LiteralPath <string[]>: Same as -Path, only wildcards are not expanded. Use this if the literal path includes a wildcard character you do not intent to expand.

-OverwriteFile: Don't warn when overwriting existing files

Receive-HL7Message

Receives a HL7 v2.x message via a TCP connection (MLLP framing).

Receive-HL7Message [-Path] <String> [-Port] <Int32> [[-Timeout] <Int32>] [[-Encoding] <String>] [-NoACK <SwitchParameter>] [-InformationAction <ActionPreference>] [-InformationVariable <String>] [<CommonParameters>]

Parameters

-Path <string>: The path to store the messages received. Must be literal path.

-Port <int>: The the TCP port to listen for messages on.

-Timeout <int>: The timeout in seconds before idle connections are dropped (defaults to 60 seconds if not specified).

-Encoding <string>: The text encoding to use when receiving the message. Supports "UTF-8" or "ISO-8859-1" (Western European). Defaults to "UTF-8" if parameter not supplied.

-NoACK <SwitchParameter>: Set this switch parameter to suppress acknowledgement (ACK) messages from being sent in reposne to messages received.

Show-HL7MessageTimeline

Lists messages chronologically based on the message header receive date/time field (MSH-7)

Show-HL7MessageTimeline -Path <string> [-Descending] [<CommonParameters>]

Parameters

-Path <string[]>: The full or relative path a single HL7 file or directory. This may include wildcards in the path name. If a directory is provide, all files within the directory will be examined. Exceptions will be raised if a file isn't identified as a HL7 v2.x file. This parameter accepts a list of files, separate each file file with a ','

-Descending: Switch to show messages in descending chronological order (defaults to ascending without this switch).

hl7-powershell-module's Issues

Remove-HL7Identifiers in Core 7 not working

Hello

The issue i am having is this commandlette isnt masking the identifiers. It is creating a new MASKED_filename.hl7 file but all of the information is left intact. FYI, this is an awesome library youve built and im very happy to be using it!.

Consider publishing on PSGallery

Hi Rob,

Awesome tool!

Would you consider publishing the module to PSGallery in future?

Consider the ability to include a list of parameters for Select-HL7Item -ItemPosition

Much like how the -Filter allow for a list of items separated by comma, it would be nice to have the ability to specifically select different HL7 segments instead of selecting all. E.g. This would return two specific segments instead of fetching all of OBR if using
-ItemPosition OBR

get-childitem *.hl7| Select-HL7Item -ItemPosition OBR-2,OBR-5 -Filter OBR-18=INSTXYZ, OBX-3[1]=analyte351

ItemValue                                                                                                                                                                                                                                            
---------                                                                                                                                                                                                                                          
123456, Invalid

Missing DLL file

Hi Rob,

I cant locate the hl7tools.dll in te files of this project.

Thanks in advance.

Why this filter does not work ?

Hi,

With this PV1 segment :
PV1||O|7601^^^XX&950110999&FINEJ^^^^^^^AA|R|||0668^^^^^^^^BB^^^^EI^ETAB&950110999&FINEJ~951105212^^^^^^^^BB^^^^ADELI^ETAB&950110999&FINEJ~10000573096^^^^^^^^BB^^^^RPPS^ETAB&950110999&FINEJ|||165||||||N|||123456789^^^BB^^ETAB&950110999&FINEJ|01|10|N|||||||||||||||||||N|||20210523140300||||||456789^^^BB^^ETAB&950110999&FINEJ
I want to extract the PV1-7.1 field value if the PV1-7.13 is equal to ADELI, then RPPS and at last EI.
If I write
Select-HL7Item -Path myHL7file.hl7 -ItemPosition PV1-7.1 -filter PV1-7.13=ADELI
I get all the PV1-7.1 values, ignoring the PV1-7.13 filter.
I tested with a dummy PV1-7.13 value : I get nothing. So the filter is used.

So what's wrong ?

Thx !

Manage several occurrences of the same segment

Hi,

I have a HL7 message with several segments OBX.
I want to loop on each of them to check the values of some fields.

$numberOfOBXSegments = (Select-HL7Item file.hl7 -ItemPosition OBX)."OBX")."OBX".Count
for ( $noSegment = 0; $noSegment -lt $numberOfOBXSegments; $noSegment++) {
  $OBX_3 =  (Select-HL7Item file.hl7 -ItemPosition OBX-3)."OBX-3")."OBX-3"[ $noSegment]
 .....
}

However, if I have 3 segments with an OBX-3 field filled only on the second one for instance, the array returned by Select-HL7Item will contain only one value (at index 0). So, I can't know it's empty on the first and last occurence.

How can I do ?

Best regards,

Dealing with HL7 files that start with a vertical tab

I am on a project where there will be millions of HL7 messages to parse. The HL7 module works great except when trying to parse the MSH because it has a vertical tab as the first character in the file. I tried to pass `vMSH in the -ItemPosition parameter, but got the following...

Select-HL7Item : �MSH-11 does not appear to be a valid HL7 item possition
At line:1 char:9

• $msh = Select-HL7Item -path "F:\Cerner Source Files\Documents\Sample ...

•     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : InvalidArgument: (�MSH-11:String) [Select-HL7Item], ArgumentException
  • FullyQualifiedErrorId : InvalidElement,HL7Tools.SelectHL7Item

As I am parsing out quite a few objects out of each file, is there a way to simply read the entire file's contents into a variable, strip off the vertical tab, and then pass this string parse the string with the HL7 module? This would save opening and closing the file 15-20 times per file.

Receive-HL7Message -NOACK

Hello! Can you please tell me what values the -NOACK parameter takes in the Receive-HL7Message command?

Filter returns more matches than expected

202208300638_001738_ORU^R01.txt

Hi

I have the attached HL7 file and I am trying to get only the OBX-3 Segments where OBX-2=NM. For this, I am using the following line but it is not restricting to the filter condition

Select-HL7Item -path <file> -ItemPosition OBX-3 -Filter OBX-2=NM

It gives me 13 matching lines when I am expecting to get only 3 lines because there are only 3 OBX matching NM as OBX-2.

Any help on clarifying what I am missing here would be very much appreciated

Thanks in Advance

Non PowerShell Users Question

We are looking for a way to roll out a tool to our users for them to test their Network connections to our Integration Engine from their servers.

While most Windows systems have PowerShell included, do you know of a way that we could make tools into an app outside of PowerShell that could easily be deployable to customers?