When sending a National Scoped ID in PID-19 (SSN) you receive "AuthorityUuid" missing error
Issue: When using the SanteDB dCDR via the HL7 ADT feed, new patients are not registered, rather you receive a NACK indicating a missing argument/parameter for AuthorityUUID
Applies To:
SanteDB dCDR Gateway Kelowna (Version 2.0.22+)
SanteDB iCDR + SanteMPI (Version 2.0.22+)
Symptoms:
Upon sending a registration using PID-19, you receive a NACK as illustrated below
Cause: This rejection is caused because the ssnAuthority has not been configured for the dCDR or iCDR.
Solutions:
If correcting the iCDR:
Open the file C:\Program Files\SanteSuite\SanteDB\Server\SanteDB.config.xml
Locate the section HL7Configuration
Add the <ssnAuthority> element (below) with the appropriate configuration of what identifier is being carried in the PID-19 field.
Save the file
Restart the SanteDB Host Process
If correcting the dCDR:
Open the file C:\WINDOWS\SYSWOW64\config\systemprofile\AppData\roaming\santedb\dcg-default\santedb.config
Locate the section HL7Configuration
Add the <ssnAuthority> element (below) with the appropriate configuration of what identifier is being carried in the PID-19 field.
Save the file
Restart the SanteDB Host Process
An appropriate ssnAuthority configuration is illustrated below:
Last updated