This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Add new RoleClass: Place of Existence

From HL7Wiki
Jump to navigation Jump to search

Note: The use-case is used as part of HL7 v3 training material.

Summary

This proposal is related to the Patient R-MIM when used for NonPersonLivingSubjects, in this case a patient of a Tree-species. In order to identify the GPS coordinates of a tree a new RolClass of 'Place of Existence' is proposed, akin to the existing class codes BIRTHPL and DEATHPL.

Use Case

Issue: geographic location of the tree (its GPS coordinates).

  • Patient.addr can't be used, the AD data type is meant to be used for a mailing address only (see R-MIM below, Patient.addr has been removed from it)
  • This is part of the patient demographics, note that trees don't move, so we're not talking about 'patient tracking'.
  • NonPersonLivingSubject has a Birthplace (BIRTHPL) role associated with it, played by E_Place which is subject of A_SpatialCoordinates.
    • Birthplace has the following definition: Relates a place (playing Entity) as the location where a living subject (scoping Entity) was born. - in this case: the place where the tree was initially planted, which may have been in a tree nursery, which isn't a very useful bit of information.
    • Place of Death (DEATHPLC) is another role of E_Place (although not used in the Patient R-MIM). It is defined as: Relates a place (playing Entity) as the location where a living subject (scoping Entity) died.

Proposal

  • Create a new Class code: EXISTENCEPL "Place of Existence", defined as "Relates an entity (player; a living subject) to a location (scoper) where it exists. The entity has to be a living subject and of a species without autonomous mobility characteristics (e.g. a tree), i.e. its location will only change through outside intervention (e.g. by humans, tornado's, etc.)". (May 2009: this part of the proposal has been accepted. Updated definition as per agreement within PA in Kyoto.)
    • The newly proposed class code is a child of: LOCE (Located Entity Role) "Relates an entity (player) to a location (scoper) at which it is present in some way. This presence may be limited in time."
    • The newly proposed class code is [the only] sibling of STOR (Stored Entity Role) "Relates an entity (player) (e.g. a device) to a location (scoper) at which it is normally found or stored when not used."
  • Add another Role (played by E_Place) to the Person part of the PA D-MIM next to Birthplace and Place of Death: associate NonPersonLivingSubject with a PlaceOfExistence role, scoped by E_Place which is subject of A_SpatialCoordinates.
    • This part of the proposal is still open.
Place of existence.gif

Discussion

  1. (WGM, January 2007) Gregg suggested to use an Encounter interaction, with an Encounter act in INT mood, and a service delivery location with an associated A_SpatialCoordinates CMET. This would convey that "all future/planned encounters with Tree X should take place at some specific GPS coordinates".
    • (René) This views place-of-existence not as an element of demographics (like address) but as an attribute of future encounters. Demographics details are genrally used to establish/determine identity: for a tree its location is one of its core characteristics which fit within scope of demographics data.
  2. (PA, WGM, Kyoto, May 2009, THU Q3): Motion to agree upon the creation of a new classcode: EXISTENCEPL with definition "Place of Existence", defined as "Relates an entity (player; a living subject) to a location (scoper) where it exists. The entity has to be a living subject and of a species without autonomous mobility characteristics (e.g. a tree), i.e. its location will only change through outside intervention (e.g. by humans, tornado's)" (motion by Alexander Henket, second Alexander de Leon, 4-0-0).
  3. (PA, WGM, Kyoto, May 2009, THU Q3): ACTION: Rene to update the proposal and submit content to the listserve.