Patient Status updated

In order to prevent state drift, and because the order of the status changed events is not guaranteed to be chronological it is recommended to request the current state of the patient from the REST API.

Example

{
  "eventType": "com.luscii.patient.status_updated.v1",
  "eventId": "{event_id}",
  "datetime": "ISO-8601", // e.g. 2024-05-14T13:33:33Z
  "organizationId": "{organizationId}",
  "payload":{
    "url": "https://api.luscii.com/v1/patients/feb8e374-4e87-40bf-b36a-a80b2c48d25c",
    "resource": { 
      "id": "{patientId}"
    },
    "statusChange": {
      "oldStatus": "{oldStatus}", // e.g. created
      "newStatus": "{newStatus}", // e.g. active
      "reason": "{reason}"
    }
  }
}

Fields

Field	Description
eventId	Unique identifier for the event being dispatched.
organizationId	Unique identifier for the organization in which the patient is created.
patientId	Unique identifier for the created patient, can be used to fetch additional information about the patient via the Public API.
oldStatus	String representation of the patient status before the change. ('active', 'created', 'cancelled', 'blocked', 'stopped')
newStatus	String representation of the patient status after the change.
reason	String description of the reason for the status change.