# PARTY as 'regular' datatype

**URL:** <https://discourse.openehr.org/t/party-as-regular-datatype/231>\
**Category:** Entity/demographics\
**Tags:** demographics\
**Created:** [11 December 2019 09:55 UTC](https://discourse.openehr.org/t/party-as-regular-datatype/231 "2019-12-11T09:55:17Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![birger.haarbrandt](https://discourse.openehr.org/user_avatar/discourse.openehr.org/birger.haarbrandt/32/24_2.png) [@birger.haarbrandt](https://discourse.openehr.org/u/birger.haarbrandt)\
**Post date:** [11 December 2019 09:55 UTC](https://discourse.openehr.org/t/party-as-regular-datatype/231/1 "2019-12-11T09:55:17Z")

</div>

Hi everybody,

I come across some cases where I think it would be beneficial if we could put an item of type Party into an Archetype. For example, the multimedia resource archetype has a field “author” that allows to capture information about the creator of a resource. Just using a URI instead of a DV\_TEXT might be insufficient. Of course we might build an internal cluster and put a string and an URI together to build our own PARTY subtitute. Though, this does not seem to be an elegant approach. Any thoughts on this? (I apologize if this has been discussed before, Slack did not provide any hints on this kind of discussion)

Best,

Birger

---

<div class="post-metadata">

**Author:** ![sebastian.iancu](https://discourse.openehr.org/user_avatar/discourse.openehr.org/sebastian.iancu/32/31_2.png) [@sebastian.iancu](https://discourse.openehr.org/u/sebastian.iancu)\
**Post date:** [11 December 2019 10:04 UTC](https://discourse.openehr.org/t/party-as-regular-datatype/231/2 "2019-12-11T10:04:47Z")

</div>

Normally you should use PARY\_REF of PARTY\_IDENTIFIED. Problem is that is not (easily) available while creating the archetype, you might want to consider attributes like composer, provider, other\_participant, etc for that. You could also use DV\_IDENTIFIER, and use type=PARTY.  
On the other hand if you would like to go for URI, the problem is that we don’t have yet a standard way of referring to a PARTY in URI format (as we have for EHR content, via DV\_EHR\_URI). There is an ongoing discussion-topic inside SEC about this, hopefully we’ll have soon more info about this.

---

<div class="post-metadata">

**Author:** ![birger.haarbrandt](https://discourse.openehr.org/user_avatar/discourse.openehr.org/birger.haarbrandt/32/24_2.png) [@birger.haarbrandt](https://discourse.openehr.org/u/birger.haarbrandt)\
**Post date:** [11 December 2019 10:10 UTC](https://discourse.openehr.org/t/party-as-regular-datatype/231/3 "2019-12-11T10:10:18Z")

</div>

Thanks Sebastian. The issue is that composer, provider etc. don’t seem to be feasible as they are related to the composition and not the pdf document, CDA whatever that can be stored inside the composition. I assume that Heather and Ian considered these option when creating the Archetype.

The issue with URI is that I cannot “hard-code” additional information. From a medico-legal perspective, onyl relying on an URI is not feasible.

---

<div class="post-metadata">

**Author:** ![sebastian.iancu](https://discourse.openehr.org/user_avatar/discourse.openehr.org/sebastian.iancu/32/31_2.png) [@sebastian.iancu](https://discourse.openehr.org/u/sebastian.iancu)\
**Post date:** [11 December 2019 14:14 UTC](https://discourse.openehr.org/t/party-as-regular-datatype/231/4 "2019-12-11T14:14:49Z")

</div>

What kind of additional information you would like to record?

---

<div class="post-metadata">

**Author:** ![birger.haarbrandt](https://discourse.openehr.org/user_avatar/discourse.openehr.org/birger.haarbrandt/32/24_2.png) [@birger.haarbrandt](https://discourse.openehr.org/u/birger.haarbrandt)\
**Post date:** [11 December 2019 14:32 UTC](https://discourse.openehr.org/t/party-as-regular-datatype/231/5 "2019-12-11T14:32:09Z")

</div>

At least a person’s name would be good.

---

<div class="post-metadata">

**Author:** ![sebastian.iancu](https://discourse.openehr.org/user_avatar/discourse.openehr.org/sebastian.iancu/32/31_2.png) [@sebastian.iancu](https://discourse.openehr.org/u/sebastian.iancu)\
**Post date:** [19 December 2019 11:07 UTC](https://discourse.openehr.org/t/party-as-regular-datatype/231/6 "2019-12-19T11:07:03Z")

</div>

Still thinking on this subject …  
Would something useful to have something like DV\_PARTYxxx, having PARTY\_IDENTIFIED or PARTY\_PROXY as value ?

---

<div class="post-metadata">

**Author:** ![ian.mcnicoll](https://discourse.openehr.org/user_avatar/discourse.openehr.org/ian.mcnicoll/32/4430_2.png) [@ian.mcnicoll](https://discourse.openehr.org/u/ian.mcnicoll)\
**Post date:** [19 December 2019 11:28 UTC](https://discourse.openehr.org/t/party-as-regular-datatype/231/7 "2019-12-19T11:28:06Z")

</div>

I think having PARTY\_IDENTIFED as a data value would be very helpful, along with adding role and organisation as attributes, and having other\_details ITEM\_TREE. I know we should be trying to manage all of this as references but it is practically impossible in many/most projects I am working on for now.

---

<div class="post-metadata">

**Author:** ![sebastian.iancu](https://discourse.openehr.org/user_avatar/discourse.openehr.org/sebastian.iancu/32/31_2.png) [@sebastian.iancu](https://discourse.openehr.org/u/sebastian.iancu)\
**Post date:** [19 December 2019 12:38 UTC](https://discourse.openehr.org/t/party-as-regular-datatype/231/8 "2019-12-19T12:38:37Z")

</div>

Indeed you/we mentioned it in last SEC meetings (or we touched briefly this subject) - just that the use case wasn’t clear for everybody at that time. Perhaps we should elaborate a bit more, get an idea about the proposition and its impact. Introducing a new DV\_x is not trivial, but can it be done if we have sufficient good reasons.

---

<div class="post-metadata">

**Author:** ![sebastian.iancu](https://discourse.openehr.org/user_avatar/discourse.openehr.org/sebastian.iancu/32/31_2.png) [@sebastian.iancu](https://discourse.openehr.org/u/sebastian.iancu)\
**Post date:** [21 September 2020 11:01 UTC](https://discourse.openehr.org/t/party-as-regular-datatype/231/9 "2020-09-21T11:01:18Z")

</div>

there is a follow up topic: [https://discourse.openehr.org/t/party-data-in-ehr-space/985](https://discourse.openehr.org/t/party-data-in-ehr-space/985)

---

<div class="post-metadata">

**Author:** ![yampeku](https://discourse.openehr.org/user_avatar/discourse.openehr.org/yampeku/32/25_2.png) [@yampeku](https://discourse.openehr.org/u/yampeku)\
**Post date:** [23 September 2020 19:33 UTC](https://discourse.openehr.org/t/party-as-regular-datatype/231/10 "2020-09-23T19:33:06Z")

</div>

I’m fine with it as long as we don’t end with an empty class…

---

<div class="post-metadata">

**Author:** ![ian.mcnicoll](https://discourse.openehr.org/user_avatar/discourse.openehr.org/ian.mcnicoll/32/4430_2.png) [@ian.mcnicoll](https://discourse.openehr.org/u/ian.mcnicoll)\
**Post date:** [18 November 2020 10:33 UTC](https://discourse.openehr.org/t/party-as-regular-datatype/231/11 "2020-11-18T10:33:37Z")

</div>

Taking this thread in a slightly different direction, part of the original problem is that we are often asked to refer to external parties in various parts of the data model without any gurantee that we can resolve these to an actual demographic service entity.

This often involved slotting in cluster pseudo-demographic slots and associated clusters which is ugly and confusing for newbies.

However, I have re-visiting the existing palaces that PARTY\_PROXY appears in an ENTRY and I think a couple of adjustments might solve a lot of the issues.

A major gap in PARTY\_IDENTIFIED is the lack of an attribute for role/relationship, alongside name and identifier, as ‘minimal clinically useful info’ where a full hookup to a demographics service is not possible or needed. However PARTY\_RELATIONSHIP does support that, albeit that it requires a coded\_text.

Should PARTY\_IDENTIFIED by extended with a new relationship/role attribute (DV\_TEXT) or should we make use of PARTY\_RELTIONSHIP to include professional relationships as well as personal.

The other addition would be to add an other\_details structure to PARTY\_IDENTIFIED. In particular it opens up the use of other\_participants to carry those snippets of contact number, address, org details that integration often forces upon us.

So

add relationship 0…\* to PARTY\_IDENTIFIED (or widen scope of PARTY\_RELATIONSHIP)  
add other\_details to PARTY\_IDENTIFIED.

---

<div class="post-metadata">

**Author:** ![thomas.beale](https://discourse.openehr.org/user_avatar/discourse.openehr.org/thomas.beale/32/35_2.png) [@thomas.beale](https://discourse.openehr.org/u/thomas.beale)\
**Post date:** [18 November 2020 11:43 UTC](https://discourse.openehr.org/t/party-as-regular-datatype/231/12 "2020-11-18T11:43:30Z")

</div>

> [@ian.mcnicoll](#):
>
> A major gap in PARTY\_IDENTIFIED is the lack of an attribute for role/relationship, alongside name and identifier, as ‘minimal clinically useful info’ where a full hookup to a demographics service is not possible or needed. However PARTY\_RELATIONSHIP does support that, albeit that it requires a coded\_text.

I seem to remember we discussed this, although I could not find a PR for it. But it would be easy to do.

> [@ian.mcnicoll](#):
>
> Should PARTY\_IDENTIFIED by extended with a new relationship/role attribute (DV\_TEXT) or should we make use of PARTY\_RELTIONSHIP to include professional relationships as well as personal.

I would suggest not - this is a class that will only work in the demographic model to represent relationships between PARTY instances.

> [@ian.mcnicoll](#):
>
> The other addition would be to add an other\_details structure to PARTY\_IDENTIFIED. In particular it opens up the use of other\_participants to carry those snippets of contact number, address, org details that integration often forces upon us.

Technically easy to do. But it risks creating a disaster in the data, due to undisciplined copies of same / almost the same demographic data representing the same provider entities.

A better solution really would just be to add a place in an EHR for demographic objects to go (versioned), and provide a way for PARTY\_PROXY instances to point to those. Then at least you will have only one Dr Jones, one Nurse DuPont etc, rather than hundreds of copies.

---

<div class="post-metadata">

**Author:** ![ian.mcnicoll](https://discourse.openehr.org/user_avatar/discourse.openehr.org/ian.mcnicoll/32/4430_2.png) [@ian.mcnicoll](https://discourse.openehr.org/u/ian.mcnicoll)\
**Post date:** [18 November 2020 12:55 UTC](https://discourse.openehr.org/t/party-as-regular-datatype/231/13 "2020-11-18T12:55:26Z")

</div>

> [@thomas.beale](#):
>
> A better solution really would just be to add a place in an EHR for demographic objects to go (versioned), and provide a way for PARTY\_PROXY instances to point to those. Then at least you will have only one Dr Jones, one Nurse DuPont etc, rather than hundreds of copies.

It would absolutely be a better option but we very frequently have no choice - typical example is a lab message that contains name of lab scientist an contact details. We need to have a simple way of handling this.

---

<div class="post-metadata">

**Author:** ![ian.mcnicoll](https://discourse.openehr.org/user_avatar/discourse.openehr.org/ian.mcnicoll/32/4430_2.png) [@ian.mcnicoll](https://discourse.openehr.org/u/ian.mcnicoll)\
**Post date:** [18 November 2020 13:04 UTC](https://discourse.openehr.org/t/party-as-regular-datatype/231/14 "2020-11-18T13:04:06Z")

</div>

@Thomas - I was a bit confused about what you were suggesting re adding ‘role’ somewhere. Sorry it is me being dense.

Did you mean that you favoured adding a role 0…\* [dv\_text] attribute to PARTY\_IDENTIFIED?

---

<div class="post-metadata">

**Author:** ![thomas.beale](https://discourse.openehr.org/user_avatar/discourse.openehr.org/thomas.beale/32/35_2.png) [@thomas.beale](https://discourse.openehr.org/u/thomas.beale)\
**Post date:** [18 November 2020 14:22 UTC](https://discourse.openehr.org/t/party-as-regular-datatype/231/15 "2020-11-18T14:22:25Z")

</div>

> [@ian.mcnicoll](#):
>
> Did you mean that you favoured adding a role 0…\* [dv\_text] attribute to PARTY\_IDENTIFIED?

Yes. This seems reasonable to me - in fact I thought we had had a discussion that was close to agreeing this…

If we did this, and it wipes out say 70% of the current ‘difficulties’ then I think this would be a good start.

---

<div class="post-metadata">

**Author:** ![thomas.beale](https://discourse.openehr.org/user_avatar/discourse.openehr.org/thomas.beale/32/35_2.png) [@thomas.beale](https://discourse.openehr.org/u/thomas.beale)\
**Post date:** [18 November 2020 14:23 UTC](https://discourse.openehr.org/t/party-as-regular-datatype/231/16 "2020-11-18T14:23:41Z")

</div>

> [@ian.mcnicoll](#):
>
> It would absolutely be a better option but we very frequently have no choice - typical example is a lab message that contains name of lab scientist an contact details. We need to have a simple way of handling this.

Good point - I presume this is a/the case where you also have ‘role’ in the incoming message and nowhere to put it in the openEHR target?

---

<div class="post-metadata">

**Author:** ![ian.mcnicoll](https://discourse.openehr.org/user_avatar/discourse.openehr.org/ian.mcnicoll/32/4430_2.png) [@ian.mcnicoll](https://discourse.openehr.org/u/ian.mcnicoll)\
**Post date:** [18 November 2020 14:33 UTC](https://discourse.openehr.org/t/party-as-regular-datatype/231/17 "2020-11-18T14:33:26Z")

</div>

It is a very common ‘minimum’ bit of this kind of demographic info.

That would be a great start but we still need to find a way to handle other tel. contact details, organisation names etc where we need to capture the incoming information without having access to a proper external reference.

Not having this flexibility is forcing us to work around the limitations by adding hacky cluster archetypes, when we should be able to make a lot more appropriate use of the provider, other\_participants. We would still need some clusters but we can embed them within the context of proper Demographic models and archetypes or mirrored DEMOGRAPHIC/EHR cluster archetypes.

---

<div class="post-metadata">

**Author:** ![ian.mcnicoll](https://discourse.openehr.org/user_avatar/discourse.openehr.org/ian.mcnicoll/32/4430_2.png) [@ian.mcnicoll](https://discourse.openehr.org/u/ian.mcnicoll)\
**Post date:** [18 November 2020 14:41 UTC](https://discourse.openehr.org/t/party-as-regular-datatype/231/18 "2020-11-18T14:41:12Z")

</div>

Typical current example - Cancer MDT referral. Job is to import into a CDR from a traditional database. We might have some sort of provider demographics service but not clear yet. Even if we do, it is still very helpful to be able to show in the template that we can ‘meet the requirements’ even if in practice the GP email details are not eventually modelled in-line.

 ![image](https://discourse.openehr.org/uploads/default/original/1X/26249f0e315af7259060230c145b5e16d40a0617.png)

---

<div class="post-metadata">

**Author:** ![thomas.beale](https://discourse.openehr.org/user_avatar/discourse.openehr.org/thomas.beale/32/35_2.png) [@thomas.beale](https://discourse.openehr.org/u/thomas.beale)\
**Post date:** [18 November 2020 14:47 UTC](https://discourse.openehr.org/t/party-as-regular-datatype/231/19 "2020-11-18T14:47:20Z")

</div>

> [@ian.mcnicoll](#):
>
> That would be a great start but we still need to find a way to handle other tel. contact details, organisation names etc where we need to capture the incoming information without having access to a proper external reference.

Note that my solution above is a new one: to add PARTY objects to individual EHRs, not to rely on a separate Demographic service (which we should have but don’t). Putting them at the root of the EHR is a kind of hybrid - it creates a mini-Demographic DB inside each EHR, which at least means:

- only one copy of each distinct identity for that EHR, i.e. only one instance of a particular Dr Jane Smith rather than say 50, corresponding to all the visits done with Dr Smith during 3 pregnancies;
- ability to use real PARTY classes
- ability to compare PARTY objects stored in EHRs across EHRs, and potentially detect errors, commonalities, and maybe extract out a proper demographic DB image later on;
- at runtime, you could use the EHR’s private demographics as a picklist for demographic entity when creating a new PARTY\_IDENTIFIED attached to an Entry.

This is an ‘idea’, not an advanced design, at this stage. If we actually did it, we could either abandon PARTY\_IDENTIFIED, or keep using it, and just treat it as a short summary copy of the most useful bits of data from the PARTY it points to (within the same containing EHR).

---

<div class="post-metadata">

**Author:** ![ian.mcnicoll](https://discourse.openehr.org/user_avatar/discourse.openehr.org/ian.mcnicoll/32/4430_2.png) [@ian.mcnicoll](https://discourse.openehr.org/u/ian.mcnicoll)\
**Post date:** [18 November 2020 15:01 UTC](https://discourse.openehr.org/t/party-as-regular-datatype/231/20 "2020-11-18T15:01:02Z")

</div>

That’s worth considering further but in most of the integration projects I have been asked to get involved with , it would still be beyond the scope of what we are asked/funded to do. It requires a whole other layer of governance when all that is really required (for good or bad) is to add some snippets of practical and orienting provider details embedded in the messages.

[Next page](https://discourse.openehr.org/t/party-as-regular-datatype/231.md?page=2)
