Uploaded image for project: 'Specifications: Reference Model'
  1. SPECRM-80

Improve description of system_id field in EHR, AUDIT_DETAILS and FEEDER_AUDIT_DETAILS

    Details

    • Type: Change Request
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: Release 1.0.3
    • Fix Version/s: Release 1.0.4
    • Component/s: Core IMs
    • Labels:
      None
    • Impact Analysis:
      None - documentation changes only.
    • Change Description:
      Hide
      Updated the following:
      - Architecture Overview section with the text:
      6.1 The EHR System
      The notion of a logical EHR system is central to the openEHR architecture. In openEHR, a system is understood as a distinct logical repository corresponding to an organisational entity that is legally responsible for the management and governance of the healthcare data contained within. This may be a regional health service that serves multiple provider enterprises or a single provider enterprise such as a larger hospital. The 'system' is therefore in general distinct from specific applications and also from provider organisations, even if in some cases it happens to be owned by a single provider. It is also distinct from any underlying virtualisation infrastructure or cloud computing facility, which may house multiple logical EHR systems in a multi-tenant fashion. This is clear by comparing the legal responsibilities of the infrastructure provider, which are for generic IT service management to a procurer, which may be a healthcare data management entity. It is the latter that undertakes legal responsibility for the content, on behalf of one or more healthcare provider organisations.
      The technical criterion for identifying an EHR system is that it is the entity that assigns version identifiers within a repository.
      6.1.1. System Identity
      Within the openEHR architecture, a system_id attribute is recorded both within each patient EHR (EHR class), and also within the audit created with each commit of data to an EHR (AUDIT_DETAILS class). This identifier identifies the logical EHR system as described above, and may be of any form. Common forms include the reverse domain name and plain and structured string identifiers. The system identifier is not assumed to be directly processable, but may instead be used as a key, for example in a service maintaining location information.

      - The EHR IM, section 4.2.1 The Root EHR Object, add the following text:
      The system_id attribute is used to record the identifier of the logical EHR repository to which the data containing the audit are committed. WHat constitutes a 'system' in this context is described in more detail in the Architecture Overview.

      - Common RM, section 4.2.3.1 Audit Details add the text:
      The system_id attribute is used to record the identifier of the logical EHR repository to which the data containing the audit are committed. WHat constitutes a 'system' in this context is described in more detail in the Architecture Overview.
      Show
      Updated the following: - Architecture Overview section with the text: 6.1 The EHR System The notion of a logical EHR system is central to the openEHR architecture. In openEHR, a system is understood as a distinct logical repository corresponding to an organisational entity that is legally responsible for the management and governance of the healthcare data contained within. This may be a regional health service that serves multiple provider enterprises or a single provider enterprise such as a larger hospital. The 'system' is therefore in general distinct from specific applications and also from provider organisations, even if in some cases it happens to be owned by a single provider. It is also distinct from any underlying virtualisation infrastructure or cloud computing facility, which may house multiple logical EHR systems in a multi-tenant fashion. This is clear by comparing the legal responsibilities of the infrastructure provider, which are for generic IT service management to a procurer, which may be a healthcare data management entity. It is the latter that undertakes legal responsibility for the content, on behalf of one or more healthcare provider organisations. The technical criterion for identifying an EHR system is that it is the entity that assigns version identifiers within a repository. 6.1.1. System Identity Within the openEHR architecture, a system_id attribute is recorded both within each patient EHR (EHR class), and also within the audit created with each commit of data to an EHR (AUDIT_DETAILS class). This identifier identifies the logical EHR system as described above, and may be of any form. Common forms include the reverse domain name and plain and structured string identifiers. The system identifier is not assumed to be directly processable, but may instead be used as a key, for example in a service maintaining location information. - The EHR IM, section 4.2.1 The Root EHR Object, add the following text: The system_id attribute is used to record the identifier of the logical EHR repository to which the data containing the audit are committed. WHat constitutes a 'system' in this context is described in more detail in the Architecture Overview. - Common RM, section 4.2.3.1 Audit Details add the text: The system_id attribute is used to record the identifier of the logical EHR repository to which the data containing the audit are committed. WHat constitutes a 'system' in this context is described in more detail in the Architecture Overview.

      Description

      See SPECPR-99

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                thomas.beale Thomas Beale
                Reporter:
                thomas.beale Thomas Beale
                Raised By:
                Thomas Beale
                Analyst:
                Bjørn Næss, Bostjan Lah, Heath Frankel, Sebastian Garde, Sebastian Iancu, Seref Arikan, Thomas Beale
                Acceptance:
                Boštjan Lah, Diego Bosca, Erik Sundvall, Ian McNicoll, Sebastian Garde, Sebastian Iancu, Shinji KOBAYASHI
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Due:
                  Created:
                  Updated:
                  Resolved: