AuditEvent profile for OZO AAA Proxy to comply with NEN7510 standards

CareTeam profile for the OZO platform. Represents a care network consisting of healthcare professionals and informal caregivers coordinating care for a patient.

Communication profile for the OZO platform. Represents messages exchanged within the care network, linking to threads via CommunicationRequest.

CommunicationRequest profile for the OZO platform. Represents a message thread or conversation within the care network. Individual messages are Communication resources that reference this thread via partOf.

Organization profile for the OZO platform. Represents healthcare organizations (hospitals, pharmacies, general practices) that employ practitioners in the care network.

Patient profile for the OZO platform. Represents the client/patient who is the subject of care coordination between healthcare professionals and informal caregivers.

Practitioner profile for the OZO platform. Represents healthcare professionals who are part of the patient's care team.

RelatedPerson profile for the OZO platform. Represents informal caregivers (family members, friends) who are part of the patient's care network.

Task profile for the OZO platform. Represents work assignments, referrals, or action items within the care network. Tasks can be linked to message threads via basedOn.

Device that originally created the resource

Extension to specify a CareTeam as the sender/reply-to address for team-level messaging. This extension is needed because CommunicationRequest.sender does not allow CareTeam references in FHIR R4.

W3C Trace Context span-id for distributed tracing

W3C Trace Context trace-id for distributed tracing

Types of agents in OZO audit events

Types of entities in OZO audit events

Types of sources in OZO audit events

Subtypes of audit events for OZO

Types of audit events for OZO

Example of an AuditEvent for Practitioner accessing Communication resources

Example of an AuditEvent for Practitioner Mark Benson accessing Communication resources

Example of an AuditEvent for a successful REST create operation through OZO AAA Proxy

Example of an AuditEvent for a REST search operation through OZO AAA Proxy

Example of an AuditEvent for a failed REST update operation through OZO AAA Proxy

Example of an AuditEvent for RelatedPerson accessing Communication resources

Example of an AuditEvent for a system-to-system access through OZO AAA Proxy

Example of a clinic team used for team-level messaging. This CareTeam represents the clinic as a whole for shared inbox functionality.

Example of a pharmacy team used for team-level messaging. This CareTeam represents the pharmacy as a whole for shared inbox functionality.

Device representing the OZO AAA Proxy instance

Reply from the clinic to the pharmacy. A practitioner from the clinic responds - the sender is the individual (for auditability) while the recipient is the pharmacy CareTeam (read from CommunicationRequest.sender for reply-to address).

First message in the thread - the initial question from the pharmacy practitioner. The sender is the individual practitioner (for auditability) while the recipient is the clinic CareTeam (for shared inbox).

Follow-up from a different practitioner at the pharmacy. This demonstrates that multiple team members can participate in the same thread. Note that the sender is a different practitioner from the original requester.

Example of a team-to-team CommunicationRequest where a pharmacy sends a message to a clinic. The senderCareTeam extension specifies the pharmacy team as the reply-to address for team-level authorization. The requester is the individual practitioner who initiated the thread for auditability.