When a patient is created in the Back-end System, the Patient data can be automatically transmitted to Noah so that when the Patient arrives physically he/she is already in the Noah database.
The import of data to Noah also follows the PatientExport.XSD and it is allowed for the BEWS to insert Noah actions in the database as well. For example if the user creates a Hearing Loss curve in an application that is not Noah compatible and wishes for the Hearing Loss to be entered into Noah, this can be done by converting the data to format 500 and transmitting it to Noah via the BEWS.
The Noah flow (decision tree) when importing data into Noah can be seen in Appendix 2: Import flow in this document. It can be important to understand in order to follow what happens with data in Noah.
Import of actions
Please note that when Noah data – like an audiogram – is imported into Noah via BEWS, the data will be imported as created by the Back-end system.
This means that when the user clicks on the action in the session browser, then Noah will not know which module created it, and will try to create a list of modules that can read the data. Normally the user will then select the preferred module to read the data.
For Audiogram actions this will work well since most data can be read by any Audiogram module. When it comes to fitting data it is a little more complex, as many fitting modules will be able to read the public part but may not be the module with which the fitting action was performed.