Skip to content

Link Method CodeSystem Code system

Canonicalhttps://fhir.apps.health/CodeSystem/nexus-link-method
Statusdraft · 1.33.0
Contentcomplete
SourceFSH · JSON

How a record was linked to (or unlinked from) its target: by a matching service alone, by a matching service whose proposal a person accepted, or by a person alone.

Carried by the nexus-link-method extension on Provenance.activity. The activity itself is the ISO 21089 record-lifecycle event link or unlink (http://terminology.hl7.org/CodeSystem/iso-21089-lifecycle), which says WHAT happened in a vocabulary any reader can interpret. These codes say HOW. They qualify that event -- each applies to a link and to an unlink alike -- and are not narrower kinds of it.

Recorded, never inferred. A Provenance for a link or unlink carries one of these codes; a reader must not deduce the method from which agents are present. Correcting a misfiled record is an unlink from the wrong target followed by a link to the right one, each with its own method.

What the match was made on, and how confident the matcher was, are separate facts and are not carried here.

CodeDisplayDefinition
automaticLinked automaticallyA matching service made the link (or unlink) with no human decision. The Provenance names the service as a Device agent.
confirmedProposed by a matcher, accepted by a personA matching service proposed the target and a person accepted it. Both are agents on the Provenance: the service as a Device, and the person who accepted, typed `verifier`.
manualLinked by a personA person chose the target, and no matcher decision was used. A matcher may have run and been overridden; if so it MAY still be named as an agent, but the link is the person's.