Whether the provincial client registry holds this patient, as far as this EMR has been able to
establish by sending it.
Set true once the registry has accepted an add for the patient, and also when the registry
refuses that add as a duplicate of a client it already holds -- both outcomes mean the same thing
for a reader, which is that the registry has a record. It is not set from a read of the registry
and it is never set speculatively.
Absent and false mean the same thing: not known to be in the registry. The value is only ever
written true; nothing writes false, so a reader should treat the absence of this extension as
the negative case rather than looking for one.
This is not a statement about the patient. It says nothing about whether a person is registered
provincially, whether their coverage is valid, or whether the registry's record agrees with this
one. It records the state of one outbound transmission, and a consumer reading it as a clinical or
administrative fact about the patient has read something it does not say.
It gates provincial reporting that depends on the registry. Estate surfaces that must not send
a provincial message about a patient the registry has never seen -- an appointment arrival, for
instance -- wait on this flag rather than sending and being refused. That is why it is stamped on
the chart at all rather than kept in the integration's own store: the surfaces that need it read
the patient, not the integration.
MIGRATION. Nexus EMR writes this extension today at http://services.well.com/fhir/pcr/exists
(FHIR-381): that address is live in stored patient records and in code, and is under migration to
the canonical declared here. Write the canonical; when reading, match both addresses exactly -- the
two share no segment, so a suffix rule does not reach the pre-migration one.
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Comments
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Source of the definition for the extension code - a logical name or a URL.
Comments
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
True once the registry has accepted this patient; absent otherwise
Definition
True when the provincial client registry has accepted an add for this patient, or has refused one as a duplicate of a client it already holds. Only true is written: absent means not known to be in the registry, and so does false.