Filing State Tag CodeSystem Code system¶
| Canonical | https://fhir.apps.health/CodeSystem/nexus-filing-state |
|---|---|
| Status | draft · 1.33.0 |
| Content | complete |
| Source | FSH · JSON |
Where an incoming record stands in being filed to a patient's chart, carried as a tag on the
record's meta.tag where this is the tag's system. One state is defined: awaiting-patient, for
a record that has arrived but has not yet been matched to a patient. One code system serves every
source of unmatched records, whatever their resource type.
It is what makes a missing subject legitimate, where a profile adopts it. A DiagnosticReport
or Observation must carry a subject unless it carries awaiting-patient
(nexus-subject-unless-awaiting-patient); so must a DocumentReference that is not a form template
(nexus-documentreference-subject-unless-template). A record carrying awaiting-patient must not
carry a subject (nexus-awaiting-patient-has-no-subject).
Matching clears it. Filing the record to a patient sets subject and removes the coding in the
same write.
Absence means filed, where a profile's invariants say so. An untagged DocumentReference that is
not a form template has a subject. Do not infer the tag from a missing subject alone: a form
template has none either.
A workflow marker, not a status or a security label. The resource's own status elements keep describing the record itself, and the tag grants or withholds no access.
At most one coding under this system. Writers replace it rather than appending; a reader should take the first and not reconcile two.
| Code | Display | Definition |
|---|---|---|
awaiting-patient | Awaiting patient | The record has arrived but has not been matched to a patient. It carries no subject and is on no patient's chart; it waits in the inbox until someone files it. Filing it sets the subject and removes this coding in the same write. |