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

FHIR IG Statistics: Requirements/PHRSFMR2-RI.1.3.3

Packagehl7.ehrs.uv.phrsfmr2
TypeRequirements
IdPHRSFMR2-RI.1.3.3
FHIR VersionR5
Sourcehttp://hl7.org/ehrs/uv/phrsfmr2/https://build.fhir.org/ig/HL7/phrsfm-ig/Requirements-PHRSFMR2-RI.1.3.3.html
URLhttp://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-RI.1.3.3
Version2.0.1-ballot
Statusactive
Date2025-04-03T15:15:30+00:00
NameRI_1_3_3_Manage_Record_Entry_Succession_and_Version_Control
TitleRI.1.3.3 Manage Record Entry Succession and Version Control (Function)
Authorityhl7
DescriptionManage successive Record Entry versions over time.
PurposeThe system must have a mechanism to handle versions and succession of Record Entries (such as a preliminary and final laboratory reports, amended or corrected documents). Versioning and succession management is based on Record Entry content, and/or status change over time. A version may be one of: 1) A completed and attested Record Entry; 2) A Record Entry completed and attested which has been modified one or more times; 3) A Record Entry that has been viewed for clinical decision-making purposes by an individual other than the author; 4) A Record Entry that has been captured in an incomplete state per organization business rules and updated over time (i.e., a preliminary laboratory test); 5) A Record Entry that electively, according to the author, must be preserved in the current state at a given point in time (i.e., History and Physical). Certain types of Record Entries are typically handled in versions, for example: - Laboratory results (preliminary and final) - Dictated reports - Work ups (over course of days) The prior version of Record Entries should be retained for the legally prescribed timeframe as defined by scope of practice, organizational policy, and jurisdictional law.

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:

Manage successive Record Entry versions over time.

Description I:

The system must have a mechanism to handle versions and succession of Record Entries (such as a preliminary and final laboratory reports, amended or corrected documents). Versioning and succession management is based on Record Entry content, and/or status change over time.

A version may be one of: 1) A completed and attested Record Entry; 2) A Record Entry completed and attested which has been modified one or more times; 3) A Record Entry that has been viewed for clinical decision-making purposes by an individual other than the author; 4) A Record Entry that has been captured in an incomplete state per organization business rules and updated over time (i.e., a preliminary laboratory test); 5) A Record Entry that electively, according to the author, must be preserved in the current state at a given point in time (i.e., History and Physical).

Certain types of Record Entries are typically handled in versions, for example:

  • Laboratory results (preliminary and final)
  • Dictated reports
  • Work ups (over course of days)

The prior version of Record Entries should be retained for the legally prescribed timeframe as defined by scope of practice, organizational policy, and jurisdictional law.

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

The system SHOULD provide the ability to manage Record Entries that become new versions when their state changes (e.g., augmented, amended, corrected, etc.).

RI.1.3.3#02 SHALL

The system SHALL provide the ability to update a Record Entry and save it as a new version.

RI.1.3.3#03 SHALL

The system SHALL capture, maintain and render the date, time and user for the original and each updated version of the Record Entry.

RI.1.3.3#04 SHALL

The system SHALL manage the succession of Record Entries in chronological version order.


Source

{
  "resourceType": "Requirements",
  "id": "PHRSFMR2-RI.1.3.3",
  "meta": {
    "profile": [
      "http://hl7.org/ehrs/uv/phrsfmr2/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/phrsfmr2/Requirements/PHRSFMR2-RI.1.3.3",
  "version": "2.0.1-ballot",
  "name": "RI_1_3_3_Manage_Record_Entry_Succession_and_Version_Control",
  "title": "RI.1.3.3 Manage Record Entry Succession and Version Control (Function)",
  "status": "active",
  "date": "2025-04-03T15:15:30+00:00",
  "publisher": "EHR WG",
  "contact": [
    {
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/ehr"
        }
      ]
    }
  ],
  "description": "Manage successive Record Entry versions over time.",
  "purpose": "The system must have a mechanism to handle versions and succession of Record Entries (such as a preliminary and final laboratory reports, amended or corrected documents). Versioning and succession management is based on Record Entry content, and/or status change over time.\r\n\r\nA version may be one of: 1) A completed and attested Record Entry; 2) A Record Entry completed and attested which has been modified one or more times; 3) A Record Entry that has been viewed for clinical decision-making purposes by an individual other than the author; 4) A Record Entry that has been captured in an incomplete state per organization business rules and updated over time (i.e., a preliminary laboratory test); 5) A Record Entry that electively, according to the author, must be preserved in the current state at a given point in time (i.e., History and Physical). \r\n\r\nCertain types of Record Entries are typically handled in versions, for example:\r\n- Laboratory results (preliminary and final)\r\n- Dictated reports\r\n- Work ups (over course of days)\r\n\r\nThe prior version of Record Entries should be retained for the legally prescribed timeframe as defined by scope of practice, organizational policy, and jurisdictional law.",
  "statement": [
    {
      "extension": [
        {
          "url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean": false
        }
      ],
      "key": "PHRSFMR2-RI.1.3.3-01",
      "label": "RI.1.3.3#01",
      "conformance": [
        "SHOULD"
      ],
      "conditionality": false,
      "requirement": "The system SHOULD provide the ability to manage Record Entries that become new versions when their state changes (e.g., augmented, amended, corrected, etc.)."
    },
    {
      "extension": [
        {
          "url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean": false
        }
      ],
      "key": "PHRSFMR2-RI.1.3.3-02",
      "label": "RI.1.3.3#02",
      "conformance": [
        "SHALL"
      ],
      "conditionality": false,
      "requirement": "The system SHALL provide the ability to update a Record Entry and save it as a new version."
    },
    {
      "extension": [
        {
          "url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean": false
        }
      ],
      "key": "PHRSFMR2-RI.1.3.3-03",
      "label": "RI.1.3.3#03",
      "conformance": [
        "SHALL"
      ],
      "conditionality": false,
      "requirement": "The system SHALL capture, maintain and render the date, time and user for the original and each updated version of the Record Entry."
    },
    {
      "extension": [
        {
          "url": "http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent",
          "valueBoolean": false
        }
      ],
      "key": "PHRSFMR2-RI.1.3.3-04",
      "label": "RI.1.3.3#04",
      "conformance": [
        "SHALL"
      ],
      "conditionality": false,
      "requirement": "The system SHALL manage the succession of Record Entries in chronological version order."
    }
  ]
}