Authorizations
API Key
Body
Patient to add to the patient panel. Patients on the panel will be monitored via ADT events. If this patient already exists, it will be overwritten. Patients are never deleted; to remove a patient from the panel, set the endDate appropriately. Patient to be processed
This will be the requesting provider for medical records required to generate a care summary (or FHIR bundle, etc.) as the result of an ADT event A medical provider
Date the patient will start being monitored, in ISO-8601 format yyyy-MM-dd. Only panels generated on or after this date will include this patient. Defaults to current date.
"2024-11-05"
Date the patient will stop being monitored, in ISO-8601 format yyyy-MM-dd. If not null, only panels generated on or before this date will include this patient
"2025-11-05"
Identifier which can be used to logically group requests together. Do not populate if you do not need to group requests together. Will default to a UUID it not populated
"BATCH-123"
All active diagnoses (problems) known about the patient. Must all be ICD-10 codes. If the patient is an existing patient then this list should be populated with all known diagnoses
All active diagnoses (problems) known about the patient. Must all be ICD-9 codes. If the patient is an existing patient then this list should be populated with all known diagnoses. ICD-10 should be greatly preferred if available.
[
{
"code": "401.1",
"displayName": "Benign essential hypertension",
"date": "2023-12-12"
}
]
All active diagnoses (problems) known about the patient. Must all be SNOMED codes. If the patient is an existing patient then this list should be populated with all known diagnoses. ICD-10 should be greatly preferred if available.
[
{
"code": "34713006",
"displayName": "Vitamin D deficiency",
"date": "2023-11-12"
}
]
All known medications for the patient
Additional information provided about the patient
Whether patient consent has been obtained to register and/or share their data them in specific contexts. Some HIEs require consent information to register patients. It is important to include non-positive consent, as in some cases, those patients may still be eligible to have some information shared in emergencies.
Response
Success
Unique Connective Health identifier to correlate subsequent processing or troubleshooting
"9e923da0-f3cb-4d2b-9fbb-17417104ffd0"