Details

    • Type: Change Request
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Release 1.0
    • Component/s: openehr.rm.ehr
    • Labels:
      None
    • Change Description:
      Hide
      Changes are as follows:
      - Add class EHR_STATUS defined as follows:

      class EHR_STATUS
      inherit LOCATABLE
      is_queryable: Boolean
      is_updatable: Boolean
      data: ITEM_STRUCTURE -- archetypable

      end

      - we also make a VERSIONED_EHR_STATUS type as
        VERSIONED_OBJECT[EHR_STATUS]

      - add attribute to EHR as follows - summary[1]: VERSIONED_EHR_STATUS

      - move attribute EHR.subject to EHR_STATUS, allowing this attribute to be
        changed and versioned

      - add an attribute ehr_id: OBJECT_ID to EHR class

      - remove inheritance of LOCATABLE in EHR

      In the data attribute, the archetype can be used to model things like:
      - deceased
      - active patient
      - etc
      Show
      Changes are as follows: - Add class EHR_STATUS defined as follows: class EHR_STATUS inherit LOCATABLE is_queryable: Boolean is_updatable: Boolean data: ITEM_STRUCTURE -- archetypable end - we also make a VERSIONED_EHR_STATUS type as   VERSIONED_OBJECT[EHR_STATUS] - add attribute to EHR as follows - summary[1]: VERSIONED_EHR_STATUS - move attribute EHR.subject to EHR_STATUS, allowing this attribute to be   changed and versioned - add an attribute ehr_id: OBJECT_ID to EHR class - remove inheritance of LOCATABLE in EHR In the data attribute, the archetype can be used to model things like: - deceased - active patient - etc
    • Approved By:
      ARB

      Description

      The EHR class includes subject and time_created. But there is a need for
      an ehr_id distinct from the subject id. All EHRs have their own id, but
      in reality, two EHRs could have the same subject id, due to errors that
      occur in real systems, data entry etc. Also, subject id needs to be
      versioned (sometimes it turns out that the data of the EHR is correct, but
      the subject id has to be changed, e.g. the current one is a duplicate for
      the same patient and is being dropped).

      Aloso, currently there is no clear place to store EHR management data e.g.
      - active/inactive status
      - merged status
      - patient inactive / not under care (therefore cancel notifications)

      Creating a standardised versioned object for this purpose would allow
      EHR-level atributes to be versioned, and openEHR software to interoperate
      with data in different EHRs.

        Attachments

          Activity

            People

            • Assignee:
              OLDthomasbeale JeffJ
              Reporter:
              heath.frankel Heath Frankel
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: