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

Correct modelling inconsistency of every EXTRACT_CHAPTER being related to a single Entity

    Details

    • Type: Change Request
    • Status: Closed
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: Release 1.0.2
    • Fix Version/s: Release 1.0.3
    • Component/s: EHR Extract IM
    • Labels:
      None
    • Impact Analysis:
      (changes already in published spec)
    • Change Description:
      Hide
      The following changes are made to the model:
      - a subtype of EXTRACT_CHAPTER is added to the model called EXTRACT_ENTITY_CHAPTER
      - the class EXTRACT_ENTITY_IDENTIFIER is removed
      - the class EXTRACT_ENTITY_MANIFEST is augmented with the attributes:
          - extract_id_key[1]: String // id by which this entity (usually a patient or EHR) is known in the extract
          - ehr_id[0..1]: String // EHR or EMR id
          - subject_id[0..1]: String // patient id, UPI
          - other_ids[0..1]: Hash<String, String> // other ids the subject or record may be known by
      - the class EXTRACT_ENTITY_CHAPTER has a copy of the attribute extract_id_key, to mark each such chapter with a meaningful identifier within the extract.
      Show
      The following changes are made to the model: - a subtype of EXTRACT_CHAPTER is added to the model called EXTRACT_ENTITY_CHAPTER - the class EXTRACT_ENTITY_IDENTIFIER is removed - the class EXTRACT_ENTITY_MANIFEST is augmented with the attributes:     - extract_id_key[1]: String // id by which this entity (usually a patient or EHR) is known in the extract     - ehr_id[0..1]: String // EHR or EMR id     - subject_id[0..1]: String // patient id, UPI     - other_ids[0..1]: Hash<String, String> // other ids the subject or record may be known by - the class EXTRACT_ENTITY_CHAPTER has a copy of the attribute extract_id_key, to mark each such chapter with a meaningful identifier within the extract.

      Description

      In the current specification, the EXTRACT_CHAPTER class has a mandatory entity_identifier attribute, which identifies the entity (usually patient or other demographic entity) whose data are contained in the chapter. However, a more flexible use of the model would allow some chapters to be used for purposes like common demographics.

      The modelling of entity_identifier is also problematic. Within the EXTRACT_ENTITY_MANIFEST class, it is hard-modelled to consist of openEHR-style Ehr id and subject ids, but it would be more practical to use String identifiers, and also to allow more kinds of identifier.

      The method of reference from EXTRACT_CHAPTER to EXTRACT_ENTITY_IDENTIFIER is also impractical, particularly in serialised expressions of an extract.

        Attachments

          Activity

            People

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

              Dates

              • Due:
                Created:
                Updated:
                Resolved: