Inbound ADT message supports patient suffix
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Registry Settings (PM)
- Update Client Data
Scenario 1: Validate inbound ADT message supports patient suffix via configuration setting
Specific Setup:
- Avatar HL7 must be installed.
- There must be an Inbound ADT connection for 'ADT-GENERIC'.
- The HL7iCONFIG("DEFINED_INTERFACES","ADT-GENERIC","MODE","DFLT_MODE","ADT-CONFIG","PatientAcctNum","TypeOfValue") configuration must be set to "1". This is the default value. 1 = A value assigned by an external system.
- The ClientServer routine and the HL7DataByProjectCode global must be installed into the 'USER' namespace.
- Client A must exist with no Suffix.
Steps
- Open the Registry Setting - Avatar PM/RADplus Utilities/Database Management form.
- Set registry setting 'Add Detailed Client Name' to "Y".
- Send an inbound A01/A08 message that includes a value for suffix(defined in the myAvatar's dictionary for suffix) in 'PID 5.4' segment.
- Open the Update Client Data - Avatar PM / Client Management / Client Information form.
- Validate the 'Client Name' contains the suffix sent in 'PID 5.4' segment.
- Send an inbound A01/A08 message that includes a value for suffix(not defined in the myAvatar's dictionary for suffix) in 'PID 5.4' segment.
- Open the Update Client Data - Avatar PM / Client Management / Client Information form.
- Validate the 'Client Name' does contains the suffix sent in 'PID 5.4' segment.
- Open the Registry Setting - Avatar PM/RADplus Utilities/Database Management form.
- Set registry setting 'Add Detailed Client Name' to "N".
- Send an inbound A01/A08 message that includes a value for suffix(defined in the myAvatar's dictionary for suffix) in 'PID 5.4' segment.
- Open the Update Client Data - Avatar PM / Client Management / Client Information form.
- Validate the 'Client Name' does not contain the suffix sent in 'PID 5.4' segment.
|
Topics
• HL7
|