| Name
|
A text field that indicates the name of the external health system to which axiUm is integrated.
|
| Patient Identifier
|
A text field that indicates the patient health record identifier type returned during exchanges with Redox.
Important: There are several possible patient health record identifier types and the external system you are working with may use several. Ensure you are entering the correct type.
|
| API Key
|
A text field that indicates the API key supplied by axiUm Professional Services.
|
| Source Secret
|
A text field that indicates the source secret supplied by axiUm Professional Services.
|
| Patient Search
|
A text field that indicates the unique destination ID used to send patient search queries to Redox.
|
| Clinical Summary
|
A text field that indicates the unique destination ID used to send clinical summary queries to Redox.
|
| Test Connection
|
A button that tests the Redox connection.
Note: If not successful, confirm the axiUm Communication API configuration is correct and, if necessary, contact Professional Services.
|
| Default Practice
|
The practice is used to generate clinical summaries from external patient Summary of Care files.
A drop-down list that indicates the default Practice.
|
| User / Message Group
|
Text fields that indicate the user or message group that receive a message and email notification when a new Summary of Care file is imported after syncing to a linked patient.
The ellipses are used to display the Users List or Message Groups windows and select a user and/or message group.
Note: You must configure a messenger event to enable this message and notification. For more information, see Messenger Events.
|
| The integrated EHR reports visit history for the last __ months.
|
Typically, an updated Summary of Care file is only imported to the Attachments/Consents module when users sync patient records (automatically or manually), and the external patient record indicates a new encounter has occurred.
However, you can override this behavior. If a set time has passed since a patient record’s last sync, an updated Summary of Care file will be imported when they next sync, even if no new encounters have occurred.
A text field that indicates the number of months that must have passed without sync activity.
|
Consistency of Care Setup - Field Definitions
