Adressing of i.e. discharge summaries

Heather Leslie heather.leslie at
Fri Mar 18 01:08:59 EDT 2016

Bjorn, Heath,

FYI - as part of the openEHR sprint, the results of the review feedback is that the previous COMPOSITION for Referral is now generalised to 'Request for service' - - and Discharge Summary has been generalised to 'Transfer of Care Summary' - You can see this in the history/audit trail for each archetype.

The NEHTA archetypes were aligned with those original archetypes some time ago but have not been updated since.



From: openEHR-technical [mailto:openehr-technical-bounces at] On Behalf Of Heath Frankel
Sent: Wednesday, 16 March 2016 6:52 PM
To: For openEHR technical discussions <openehr-technical at>
Subject: RE: Adressing of i.e. discharge summaries

Hi Bjorn,
Yes we have used these archetypes for representing the service request at both the instruction and composition level. Our instruction starts in a care plan so we have to represent the referred to provide in the instruction participations. Then when we send the referral we copy it to the receiving provider participation in the eReferral composition.

Since a discharge summary is a kind of transfer of care then I would expect it to have a similar participation when it is being directed to a primary care provider although this doesn't need to be populated when it is being uploaded to a national repository for example.



From: openEHR-technical [mailto:openehr-technical-bounces at] On Behalf Of Bjørn Næss
Sent: Wednesday, 16 March 2016 4:42 PM
To: openehr-technical at<mailto:openehr-technical at>
Subject: Adressing of i.e. discharge summaries

There is a lot of compositions that is created for the purpose of sending the content to another healthcare provider. Discharge summaries is one example.
For instruction health care service request there is some elements and slots added to the protocol part. Here you can add both the requestor and the identifier.

In the Nehta CKM there is a composition archetype for referral. This archetype has some structure under context to add participation and identification of the requestor. I think this pattern would be the right way to do this.

Anyone with experiences or suggestions on how to do this?

Best regards
Bjørn Næss
Product owner

Mobil +47 93 43 29 10<tel:+47%2093%2043%2029%2010>

No virus found in this message.
Checked by AVG -<>
Version: 2015.0.6189 / Virus Database: 4540/11798 - Release Date: 03/11/16
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the openEHR-technical mailing list