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

FHIR IG Statistics: Requirements/EHRSFMR2-RI.1.1.9

Packagehl7.ehrs.uv.ehrsfmr2
TypeRequirements
IdEHRSFMR2-RI.1.1.9
FHIR VersionR5
Sourcehttp://hl7.org/ehrs/uv/ehrsfmr2/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2-RI.1.1.9.html
URLhttp://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-RI.1.1.9
Version2.1.1-ballot
Statusactive
Date2025-05-13T15:11:00+00:00
NameRI_1_1_9_Receive_Retain_Record_Lifecycle_Event
TitleRI.1.1.9 Receive/Retain Record Lifecycle Event (Function)
Realmuv
Authorityhl7
DescriptionReceive/Retain Record Entries (1 or more instances)
PurposeOccurs when an agent causes the system to a) initiate capture of data content from elsewhere, and b) incorporate that content into the storage considered a permanent part of the health record. Reference: ISO 21089-2018, Section 15.9.

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:

Receive/Retain Record Entries (1 or more instances)

Description I:

Occurs when an agent causes the system to a) initiate capture of data content from elsewhere, and b) incorporate that content into the storage considered a permanent part of the health record.

Reference: ISO 21089-2018, Section 15.9.

Actors:
ehr
Criteria N:
RI.1.1.9#01 SHOULD

The system SHOULD provide the ability to capture and maintain Record Entry content from external systems, retaining and persisting original unaltered content and signature bindings, Action and Record Entry provenance and metadata.

RI.1.1.9#02 SHALL

The system SHALL provide the ability to capture and maintain Record Entry extracts from external systems, retaining and persisting source, identity, record content, corresponding provenance and metadata.

RI.1.1.9#03 SHALL

The system SHALL provide the ability to capture the identity of the patient or individual subject to whom Record Entry content was received.

RI.1.1.9#04 conditional SHOULD

IF received with Record Entry content, THEN the system SHOULD control subsequent data access to that permitted by corresponding authorizations and patient consents.


Source

{
  "resourceType": "Requirements",
  "id": "EHRSFMR2-RI.1.1.9",
  "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.9",
  "version": "2.1.1-ballot",
  "name": "RI_1_1_9_Receive_Retain_Record_Lifecycle_Event",
  "title": "RI.1.1.9 Receive/Retain 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": "Receive/Retain Record Entries (1 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 a) initiate capture of data content from elsewhere, and b) incorporate that content into the storage considered a permanent part of the health record. \n\nReference: ISO 21089-2018, Section 15.9.",
  "statement": [
    {
      "extension": [
        {
          "url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean": false
        }
      ],
      "key": "EHRSFMR2-RI.1.1.9-01",
      "label": "RI.1.1.9#01",
      "conformance": [
        "SHOULD"
      ],
      "conditionality": false,
      "requirement": "The system SHOULD provide the ability to capture and maintain Record Entry content from external systems, retaining and persisting original unaltered content and signature bindings, Action and Record Entry provenance and metadata.",
      "derivedFrom": "EHR-LM_R1 14.6.1"
    },
    {
      "extension": [
        {
          "url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean": false
        }
      ],
      "key": "EHRSFMR2-RI.1.1.9-02",
      "label": "RI.1.1.9#02",
      "conformance": [
        "SHALL"
      ],
      "conditionality": false,
      "requirement": "The system SHALL provide the ability to capture and maintain Record Entry extracts from external systems, retaining and persisting source, identity, record content, corresponding provenance and metadata.",
      "derivedFrom": "EHR-LM_R1 14.6.1"
    },
    {
      "extension": [
        {
          "url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean": false
        }
      ],
      "key": "EHRSFMR2-RI.1.1.9-03",
      "label": "RI.1.1.9#03",
      "conformance": [
        "SHALL"
      ],
      "conditionality": false,
      "requirement": "The system SHALL provide the ability to capture the identity of the patient or individual subject to whom Record Entry content was received."
    },
    {
      "extension": [
        {
          "url": "http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean": false
        }
      ],
      "key": "EHRSFMR2-RI.1.1.9-04",
      "label": "RI.1.1.9#04",
      "conformance": [
        "SHOULD"
      ],
      "conditionality": true,
      "requirement": "IF received with Record Entry content, THEN the system SHOULD control subsequent data access to that permitted by corresponding authorizations and patient consents."
    }
  ]
}