post https://fhir-api.zapehr.com/r4b/Subscription
Subscription on the FHIR specification website.
The subscription resource is used to define a push-based subscription from a server to another system. Once a subscription is registered with the server, the server checks every resource that is created or updated, and if the resource matches the given criteria, it sends a message on the defined "channel" so that another system can take an appropriate action.
The body should be a valid FHIR object for Subscription.
Here is an example:
{
"resourceType": "Subscription",
"id": "example-error",
"text": {
"status": "generated",
"div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">[Put rendering here]</div>"
},
"status": "error",
"contact": [
{
"system": "phone",
"value": "ext 4123"
}
],
"end": "2021-01-01T00:00:00Z",
"reason": "Monitor new neonatal function",
"criteria": "Observation?code=http://loinc.org|1975-2",
"error": "Socket Error 10060 - can't connect to host",
"channel": {
"type": "rest-hook",
"endpoint": "https://biliwatch.com/customers/mount-auburn-miu/on-result",
"payload": "application/fhir+json",
"header": [
"Authorization: Bearer secret-token-abc-123"
]
}
}
You can reference the FHIR documentation to determine the format for Subscription.