Harmonization Proposal: Add new EXISTENCEPL roleClass

Recommendation for HL7 RIM Change and/or Vocabulary changes	RECOMMENDATION ID:
Sponsored by: PA	Approval date by sponsor: WGM, Kyoto, May 2009, THU Q3, see Add new RoleClass: Place of Existence.
Revision (# and date): 2009-07-10	Date submitted:
Editor/Author: René Spronk	Sponsor Status: Approved
PROPOSALNAME: Add new EXISTENCEPL roleClass

Summary of Vocabulary changes

Abbrev.	Description	# to Add	# to Remove	# to Change
D	Concept Domains	0	0	0
S	Code Systems	0	0	1
C	Concept codes in a code system	1	0	0
V	Value sets	0	0	1
B	Context Bindings	0	0	0

Position of Concerned Organizations

ORG.NAME	RECOMMENDATION APPROVAL STATUS	AFFECTED ENTITIES OF INTEREST TO ORG
PA	Approved	Role.code

Issue

Issue: geographic location of the tree (its GPS coordinates). The tree is the NonLivingPerson patient. Patients can be ssociated with a Birthplace (BIRTHPLC) and a PlaceOfDeath (DEATHPLC), but not with a place where they exist.

• Patient.addr can't be used, the AD data type is -per the data vtype spec- meant to be used for a mailing address only.

Recommendation Details

• 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.)".
  • 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."

Vocabulary Recommendation(s)

In the RoleClass coding system (OID 2.16.840.1.113883.5.110), the RoleClassLocatedEntity value set (2.16.840.1.113883.1.11.16815):

• 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.)".
  • The newly proposed class code is a child of: LOCE (Located Entity Role, InternalId 16815) "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, InternalId 16817) "Relates an entity (player) (e.g. a device) to a location (scoper) at which it is normally found or stored when not used."

Rationale

PA specific aspects of the rationale: 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.

• 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 place (playing Entity) as the location where a living subject (scoping Entity) died.

Recommended Action Items

• MnM to implement the proposed solution