patient-link
type: OperationDefinition
node role: treeRoot
id:
  v: patient-link
text:
  status:
    v: generated
  div: Generated Narrative: OperationDefinition patient-link URL: [base]/Patient/$link Parameters Use Name Scope Cardinality Type Binding Documentation IN source-patient 0..1 Reference (Patient) A direct resource reference to the source patient resource (this may include an identifier). IN source-patient-identifier 0..* Identifier When source-patient-identifiers are provided, the server is expected to perform an internal lookup to identify the source patient record. The server SHALL reject the request if the provided identifiers do not resolve to a single patient record. This resolution MAY occur asynchronously, for example, as part of a review by a user. IN target-patient 0..1 Reference (Patient) A direct resource reference to the target patient resource. This is the surviving patient resource, the target for the link. IN target-patient-identifier 0..* Identifier When target-patient-identifiers are provided, the server is expected to perform an internal lookup to identify the target patient record. The server SHALL reject the request if the provided identifiers do not resolve to a single patient record. This resolution MAY occur asynchronously, for example, as part of a review by a user. OUT return 1..1 Patient The status of the response will be one of: 200 OK - If the merge request doesn't expect any issues (although warning may be present) for a preview, or was completed without issues if not a preview 202 Accepted - The merge request has been accepted and does not expect any issues and will continue processing the merge in the background, and you can monitor the Task for completion 400 Bad Request - There are errors in the input parameters that need to corrected 422 Unprocessable Entity - Business rules prevent this merge from completing The Parameters resource will include: The Input parameters to the operation An OperationOutcome containing errors, warnings, and information messages The resulting merged Patient resource (or a patient reference if the patient is not c…
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
  value: integer
    v: 1
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
  value: code
    v: trial-use
url:
  v: https://fhir.ee/mpi/OperationDefinition/patient-link
version:
  v: 1.2.1
name:
  v: EEMPIPatientLink
title:
  v: Patient Link
status:
  v: active
kind:
  v: operation
experimental:
  v: false
date:
  v: 2025-03-26T21:51:23+00:00
publisher:
  v: TEHIK
contact:
  name:
    v: TEHIK
  telecom:
    system:
      v: url
    value:
      v: https://tehik.ee
description:
  v: The link operation is used to link two patient resources. One of the two patients is identified as the source and one as the target. The link with type 'replaces' created from source to destination patient, the another link with type 'replaced-byä created from destination to source patient. As result of linking the destination patient is deactivated.
jurisdiction:
  coding:
    system:
      v: urn:iso:std:iso:3166
    code:
      v: EE
    display:
      v: Estonia
affects state:
  v: true
code:
  v: link
resource:
  v: Patient
system:
  v: false
type:
  v: true
instance:
  v: false
parameter:
  name:
    v: source-patient
  use:
    v: in
  min:
    v: 0
  max:
    v: 1
  documentation:
    v: A direct resource reference to the **source** patient resource (this may include an identifier).
  type:
    v: Reference
  target profile:
    v: http://hl7.org/fhir/StructureDefinition/Patient
    link: http://hl7.org/fhir/StructureDefinition/Patient
parameter:
  name:
    v: source-patient-identifier
  use:
    v: in
  min:
    v: 0
  max:
    v: *
  documentation:
    v: When source-patient-identifiers are provided, the server is expected to perform an internal lookup to identify the source patient record. The server SHALL reject the request if the provided identifiers do not resolve to a single patient record. This resolution MAY occur asynchronously, for example, as part of a review by a user.
  type:
    v: Identifier
parameter:
  name:
    v: target-patient
  use:
    v: in
  min:
    v: 0
  max:
    v: 1
  documentation:
    v: A direct resource reference to the **target** patient resource. This is the surviving patient resource, the target for the link.
  type:
    v: Reference
  target profile:
    v: http://hl7.org/fhir/StructureDefinition/Patient
    link: http://hl7.org/fhir/StructureDefinition/Patient
parameter:
  name:
    v: target-patient-identifier
  use:
    v: in
  min:
    v: 0
  max:
    v: *
  documentation:
    v: When target-patient-identifiers are provided, the server is expected to perform an internal lookup to identify the target patient record. The server SHALL reject the request if the provided identifiers do not resolve to a single patient record. This resolution MAY occur asynchronously, for example, as part of a review by a user.
  type:
    v: Identifier
parameter:
  name:
    v: return
  use:
    v: out
  min:
    v: 1
  max:
    v: 1
  documentation:
    v: The status of the response will be one of: * 200 OK - If the merge request doesn't expect any issues (although warning may be present) for a preview, or was completed without issues if not a preview * 202 Accepted - The merge request has been accepted and does not expect any issues and will continue processing the merge in the background, and you can monitor the Task for completion * 400 Bad Request - There are errors in the input parameters that need to corrected * 422 Unprocessable Entity - Business rules prevent this merge from completing The Parameters resource will include: * The Input parameters to the operation * An OperationOutcome containing errors, warnings, and information messages * The resulting merged Patient resource (or a patient reference if the patient is not committed) * Optionally a Task resource to track any additional processing that was required.
  type:
    v: Patient