RE: question about Party

["Sam Heard" <sam.heard@oceaninformatics.com>]

Hi Bert

Not sure if you have had discussions off line but I would say that it is the demographic service instance. The reference model documentation is clearly describing the EHR owning the composition (or something else) and it is not so clear in the demographic space as people are really a high level object.

 

It might be that a class VERSIONED_PERSON is the way to go – providing a unique space for each individual.

 

Let’s see if I can stimulate some response.

 

Cheers, Sam

 

From: openehr-implementers-bounces@openehr.org [mailto:openehr-implementers-bounces@openehr.org] On Behalf Of Bert Verhees
Sent: Wednesday, 29 July 2009 11:02 AM
To: For openEHR implementation discussions
Subject: Re: question about Party

 

In a mysterious way,m sometimes, my messages do not appear on the list, that is why I send it again

Op woensdag 29-07-2009 om 10:52 uur [tijdzone +0200], schreef Bert Verhees:

PERSON inherits from Locatable, and Locatable has the attribute ownerId.

It is not allowed to leave it empty.

Excuse me, this email was wrong, the question is valid but wrong formulated, sorry for that, I was busy in a telephone-call while sending it (multitasking)

The question I meant to ask is:
It is about storing a PERSON in a VERSIONED_OBJECT, the documentation says:

Each VERSIONED_OBJECT has a unique identifier recorded in the uid attribute (a HIER_OBJECT_ID
typically containing a GUID), and a reference to the owning object (e.g. the owning EHR) in the
owner_id attribute


Who is the owner of a PERSON (f.e. representing a patient)

Thanks
Bert