NOAH data quality is important for a correctly done NOAH patients import into Bridge 2 and subsequent Bridge 2 work with this data.
NOAH data requirements
- file(s) must be uploaded to the secure storage by the link provided by Auditdata Support
- NOAH data can be provided in either of the two formats: .nhax (non-encrypted) OR .enhax (encrypted)
- encryped data (.enhax) must be accompanied by the password. In case of several separate .enhax files, the password must be provided for each of the files
if file(s) are uploaded to the secure storage, a non-encrypted .nhax file is preferred
Import requires a mapping between the patient in the customer's OMS system and in NOAH. There are two ways to create the mapping:
- by populating EITHER Other1 or Other2 field in NOAH System with the patient's ID from the customer's OMS system
- by providing a mapping file in .csv format with NOAH patient GUID and the corresponding patient's ID from the customer's OMS system
The two ways to create a mapping can complement each other. For instance, a customer can populate the Other1 or Other2 fields with the patient's ID from OMS for some customers and at the same time provide a mapping file for other customers. If the same patient is mapped in both ways simultaneously, the mapping from EITHER Other1 or Other2 fields takes precedence during the import, which means this patient from the .csv file is ignored.
In case the customer decides to use the .csv mapping file, the following requirements apply:
- mapping file has to be saved in .csv format and have only two data pairs: NOAH patient GUID and a mapping number; separated by a comma without space.
- NOAH patient GUID is the unique identifier of any patient in NOAH. Mapping number is the unique identifier of a patient in the customer's OMS system
- mapping number in NOAH can be saved to either of the two available custom fields: Other1 or Other2
- the GUID field in the first row of the .csv file has to be named PatientGUID followed by the custom field used for saving the mapping number and separated by a comma with no space
See example of a valid .csv file below:
- if any row in the mapping file is missing either PatientGUID (GUID) or a mapping number, this patient record is skipped and will not be imported
patient record in NOAH must have a unique SessionCreateDate parameter. If a patient record contains more than one session with the same SessionCreateDate parameter, this patient is skipped during
After the main import is complete, customer can supply the delta data to be additionally imported afterwards. Delta in this scenario means the NOAH patient records that were created in customer's NOAH system AFTER the last main NOAH file export was sent to Auditdata.
Delta files must be also saved in .nhax or .enhax format and uploaded to the secure storage using the same link.