Ocean Referral Tag CodeSystem Code system¶
| Canonical | ../CodeSystem/ocean-referral-tag |
|---|---|
| Status | draft · 1.26.0 |
| Content | not-present |
| Source | FSH · JSON |
Marks a resource as having entered Nexus EMR through the Ocean eReferral integration, and names the
referral it belongs to. Carried on meta.tag, where this is the tag's system.
A tag, not an identifier element. The address identifies the system of a Coding in
meta.tag, which is why it is declared as a code system even though its values are identifiers.
The system and the code answer different questions. The presence of a tag under this system,
with the code ignored, is what says the resource came from the Ocean integration. The code says
which referral: it is the Ocean eReferral reference taken from the referral's ServiceRequest, and
every resource persisted for that referral carries the same value, so _tag=<system>|<referral>
retrieves the whole set -- the request, its communications, its attachments, and the organizations
and practitioners that arrived with it.
Content is not-present, and it is not a fragment either. The values are minted by Ocean, not
by this specification, so there is no membership to publish. Treat each value as an opaque token,
match it exactly, and do not parse it.
One older shape is still matched. Some records carry the bundle entry's full URL in place of the referral reference, and the matching path still searches for that form as a fallback. A store may hold both shapes under this one system, and neither can be derived from the other.
It is provenance, not status. The tag says where the resource entered and what it belongs to. It carries nothing about whether the referral is open, accepted or revoked, and its absence does not mean a resource was authored locally -- Ocean is one integration among several.
Nexus EMR writes this today at
http://services.well.com/fhir/tags/integration-provider/ocean (FHIR-381): it is live in stored
meta.tag codings and in code, and is under migration to the canonical declared here. Write the
canonical; expect both until the migration completes, and match both addresses exactly -- the two
share no final segment, so a suffix rule reaches neither reliably.
All codes from this system.