Appointment Invoiced Extension¶
| Canonical | ../StructureDefinition/appointment-invoiced |
|---|---|
| Status | draft · 1.26.0 |
| Base | Extension (constraint) |
| Context | Appointment (element) |
| Source | FSH · JSON |
That an invoice covering this appointment's visit has been observed at the billing vendor, and the instant it was observed.
Overview
An observation, not a workflow state. Appointment.status carries the states a clinic sets by
hand; this carries only what a read-back of the vendor confirmed. Neither can be derived from the
other, and a status that reads as billed is not evidence that this extension would be present.
Absence means the observation has not been made -- NOT that the visit was not invoiced. The extension is written only when an invoice was seen. It is absent while a read-back has not run, while it has run without finding one, and wherever no read-back exists. Rendering absence as "not invoiced" in a user interface is a defensible choice; counting it as "no invoice exists" is not, and a report built that way under-states billing coverage. Treat absence as unknown.
The instant is when the invoice was observed, not when it was raised and not when the service was delivered. The observation is not rewritten once stored, so the instant names the first confirmation rather than the most recent check.
Written at most once per appointment. A reader encountering more than one copy should take the first rather than merge them.
MIGRATION. Nexus EMR writes this extension today at
http://services.well.com/fhir/StructureDefinition/appointment-invoiced (FHIR-378). That address is
live in stored appointments and in code, and is under migration to the canonical declared here.
Write the canonical; when reading, match on the URL suffix appointment-invoiced so that
appointments filed under either address are seen.