Health-record handoff

Approving an appointment writes it into the national health record. If that record is unreachable, the appointment is still saved, queued, and retried until it lands.

Status: Live at the Pinamar installation.

The health-record queue showing retries in progress — The queue drains itself. Nobody re-enters an appointment because a system was down.

Nothing breaks because of an integration

The rule is that local state is committed first. Staff approve; the appointment exists; the handoff is a background job. A failed push is a queue entry with a retry time, not an error the front desk has to understand.

The same rule covers email and messaging: a missing key means a notification is skipped, never that a booking fails.

What gets written

The patient, the professional, the service and the slot, mapped onto the health record’s own identifiers. Patients who exist there already are matched rather than duplicated.

When the two disagree

An appointment can also be moved or cancelled inside the health record itself. A resynchroniser compares both sides and resolves the difference, so the staff panel does not keep offering a slot that no longer exists.

Next: Booking