FHIR © HL7.org  |  Server Home  |  XIG Home  |  XIG Stats  |  Server Source  |  FHIR  

FHIR IG Statistics: Requirements/EHRSFMR2-RI.1.1.20

Packagehl7.ehrs.uv.ehrsfmr2
Resource TypeRequirements
IdEHRSFMR2-RI.1.1.20
FHIR VersionR5
Sourcehttp://hl7.org/ehrs/uv/ehrsfmr2/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2-RI.1.1.20.html
URLhttp://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-RI.1.1.20
Version2.1.1-ballot
Statusactive
Date2025-05-13T15:11:00+00:00
NameRI_1_1_20_Unmerge_Record_Lifecycle_Event
TitleRI.1.1.20 Unmerge Record Lifecycle Event (Function)
Realmuv
Authorityhl7
DescriptionUnmerge Record Entries previously merged (2 or more instances)
PurposeOccurs when an agent causes the system to reverse a previous record entry merge operation, rendering them separate again. Reference: ISO 21089-2018, Section 15.20.

Resources that use this resource

No resources found


Resources that this resource uses

No resources found


Narrative

Note: links and images are rebased to the (stated) source

Statement N:

Unmerge Record Entries previously merged (2 or more instances)

Description I:

Occurs when an agent causes the system to reverse a previous record entry merge operation, rendering them separate again.

Reference: ISO 21089-2018, Section 15.20.

Actors:
ehr
Criteria N:
RI.1.1.20#01 dependent SHALL

The system SHALL provide the ability to update multiple patient Record Entries that were previously harmonized or integrated by unmerging them according to scope of practice, organizational policy, and/or jurisdictional law.


Source

{
  "resourceType": "Requirements",
  "id": "EHRSFMR2-RI.1.1.20",
  "meta": {
    "profile": [
      "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMFunction"
    ]
  },
  "text": {
    "status": "extensions",
    "div": "<!-- snip (see above) -->"
  },
  "extension": [
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode": "ehr"
    }
  ],
  "url": "http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-RI.1.1.20",
  "version": "2.1.1-ballot",
  "name": "RI_1_1_20_Unmerge_Record_Lifecycle_Event",
  "title": "RI.1.1.20 Unmerge Record Lifecycle Event (Function)",
  "status": "active",
  "date": "2025-05-13T15:11:00+00:00",
  "publisher": "HL7 International / Electronic Health Records",
  "contact": [
    {
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/ehr"
        }
      ]
    }
  ],
  "description": "Unmerge Record Entries previously merged (2 or more instances)",
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001",
          "display": "World"
        }
      ]
    }
  ],
  "purpose": "Occurs when an agent causes the system to reverse a previous record entry merge operation, rendering them separate again. \n\nReference: ISO 21089-2018, Section 15.20.",
  "statement": [
    {
      "extension": [
        {
          "url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean": true
        }
      ],
      "key": "EHRSFMR2-RI.1.1.20-01",
      "label": "RI.1.1.20#01",
      "conformance": [
        "SHALL"
      ],
      "conditionality": false,
      "requirement": "The system SHALL provide the ability to update multiple patient Record Entries that were previously harmonized or integrated by unmerging them according to scope of practice, organizational policy, and/or jurisdictional law."
    }
  ]
}