Hi Laura

 

Thanks for the link. I am finding it very difficult to make head or tail of
the pages and what it all means.

The pages appear to have a very basic 13606 element at the top and then a
heap of references including self references.

 

Can you help at all?

 

Cheers, Sam

 

From: [email protected]
[mailto:openehr-technical-bounces at openehr.org] On Behalf Of Sato Laura (NHS
CONNECTING FOR HEALTH)
Sent: Friday, 7 October 2011 11:34 PM
To: For openEHR technical discussions
Subject: RE: openEHR Archetypes Development

 

In part in (a slow!) response to the discussion below, I'm pleased to invite
comments on the current draft detailed content models (based on 13606 and
using the SNOMED CT concept model) for Discharge Summary, now accessible at
https://svn.connectingforhealth.nhs.uk/svn/public/lra/PUB/discharge/content/
index.html.  (Apologies for the certificate warning that you'll be
confronted with at first.)

 

For some background info, this work is still relatively rough - it's an
interim draft release that shows our first attempt to publish a full suite
of detailed requirements, technical models and instance examples for record
content.  We're aware of a few inconsistencies and gaps in the end-to-end
flow, but I'd still welcome any comments you might have time to send us ...
I'm hoping that we'll release the next draft (based on comments received in
the next few weeks) in November.

 

Best wishes,

Laura

 

--------------------------------------------------------

Laura Sato

Head, Logical Record Architecture

 

Department of Health Informatics Directorate

Technology Office, NHS Connecting for Health

 

email: laura.sato at nhs.net

mobile: (44) (0)7733 324 338

 

 

From: [email protected]
[mailto:openehr-technical-bounces at openehr.org] On Behalf Of Eunice Ab
Sent: 03 June 2011 12:18
To: For openEHR technical discussions
Subject: Re: openEHR Archetypes Development

 

Dear Laura, Ian

 

Many thanks for your emails. They have been so helpful .....

 

Laura, I am going to take up the offer of contacting you to get to know more
about the 'central activities'. I will be in touch soon.

 

Ian, I totally agree that most of the work done on data standards is
currently been hidden away behind the N3 firewall or through trud. We need
more accessible mechanisms for this work expecially for those that actually
need to use these standards locally.

 

Hopefully this will be taken into consideration in current and future work.

 

Thanks again.

 

Best regards

 

Eunice

 

On 3 June 2011 10:44, Ian McNicoll <Ian.McNicoll at oceaninformatics.com>
wrote:

Thanks Laura,

That is very helpful clarification. It is unfortunate that much of the
interesting work being done in the English NHS is 'hidden away' either
with the TRUD mechanism or in the case of the Clinical Data Standards
work, behind the N3 firewall. I know steps are being taken to address
these issues but it does present a significant barrier for those
outside the NHS.

Regards,


Ian

Dr Ian McNicoll
office +44 (0)1536 414 994
         +44 (0)2032 392 970
fax +44 (0)1536 516317
mobile +44 (0)775 209 7859
skype ianmcnicoll
ian.mcnicoll at oceaninformatics.com

Clinical Modelling Consultant, Ocean Informatics, UK
openEHR Clinical Knowledge Editor www.openehr.org/knowledge
Honorary Senior Research Associate, CHIME, UCL
BCS Primary Health Care  www.phcsg.org <http://www.phcsg.org/> 




On 3 June 2011 10:28, Sato Laura (NHS CONNECTING FOR HEALTH)

<laura.sato at nhs.net> wrote:
> Dear Eunice,
>
>
>
> For info, although NHS Data Standards & Products has worked with openEHR
> archetypes in the past, we are currently working on developing care record
> content models that use the EN/ISO 13606 reference model and ISO 21090
data
> types (both with a relationship to, but not exactly the same as, openEHR's
> technical infrastructure), alongside a modelling approach that seeks to
make
> as much use as possible of the SNOMED CT clinical concept hierarchy, as
well
> as re-usable ELEMENT models and terminology constraints.  Do please feel
> free to get in touch with me, if you'd like more information about current
> NHS 'central' activities in this area.
>
>
>
> We also continue communications with Thomas and Ian (and others) to
maintain
> links with the openEHR community, and hopefully will be able to provide a
> clearer picture of how NHS content and openEHR archetypes fit together in
> the coming months.
>
>
>
> Best regards,
>
> Laura
>
>
>
> --------------------------------------------------------
>
> Laura Sato
>
> Head, Logical Record Architecture
>
>
>
> Department of Health Informatics Directorate
>
> Technology Office, NHS Connecting for Health
>
>
>
> email: laura.sato at nhs.net
>
> mobile: (44) (0)7733 324 338
>
>
>
>
>
>
>
>
>
> From: openehr-technical-bounces at openehr.org
> [mailto:openehr-technical-bounces at openehr.org] On Behalf Of Eunice Ab
> Sent: 19 May 2011 18:22
> To: For openEHR technical discussions
> Subject: Re: openEHR Archetypes Development
>
>
>
> Dear Ian
>
>
>
> Thank you so much for your reply.
>
>
>
> I was thinking whether there was a centrally funded team dedicated to
> developing archetypes for data standard developers. I was wondering
> whether if one was involved in a development work for clinical systems and
> notice that new archetypes are required, whether one could request for the
> archetype development free.
>
>
>
> I can see this is not the way things work....
>
>
>
> Thanks so much.
>
>
>
> Eunice
>
> On 19 May 2011 17:22, Ian McNicoll <Ian.McNicoll at oceaninformatics.com>
> wrote:
>
> Hi Eunice,
>
>
>
> There are a variety of ways in which archetype development can be
supported.
> Many of the archetypes currently on CKM have their origins in work
supported
> and funded by the English NHS. There are other people and places doing
> development, particularly NEHTA in Australia -
> see http://dcm.nehta.org.au/ckm/# <http://dcm.nehta.org.au/ckm/>  who I
understand are funding both
> editorial and clinical review time.
>
>
>
> As you will see from my other reply, this is an emerging space and it is
> difficult to answer your question directly without knowing more about what
> you are trying to do in the NHS context. By all means email me directly if
> you want to discuss privately. I am based in the UK and reasonably
familiar
> with the various UK standards development efforts (for better or worse!!).
>
>
>
> Ian
>
>
>
> Dr Ian McNicoll
> office +44 (0)1536 414 994
>
>          +44 (0)2032 392 970
> fax +44 (0)1536 516317
> mobile +44 (0)775 209 7859
> skype ianmcnicoll
> ian.mcnicoll at oceaninformatics.com
>
> Clinical Modelling Consultant, Ocean Informatics, UK
> openEHR Clinical Knowledge Editor www.openehr.org/knowledge
> Honorary Senior Research Associate, CHIME, UCL
> BCS Primary Health Care  www.phcsg.org <http://www.phcsg.org/> 
>
> On 19 May 2011 16:26, Eunice Ab <euniceab at googlemail.com> wrote:
>
> Hi All
>
>
>
> Wondering if you could help.
>
>
>
> I wanted to confirm whether one can request for archetype development for
> free if one does not currently exist.
>
>
>
> Are there any costs associated with this?
>
>
>
> Many thanks.
>
>
>
> Eunice
>
>
>
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>
>
>
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>
>
>
>
****************************************************************************
****************************************
>
> This message may contain confidential information. If you are not the
> intended recipient please inform the
> sender that you have received the message in error before deleting it.
> Please do not disclose, copy or distribute information in this e-mail or
> take any action in reliance on its contents:
> to do so is strictly prohibited and may be unlawful.
>
> Thank you for your co-operation.
>
> NHSmail is the secure email and directory service available for all NHS
> staff in England and Scotland
> NHSmail is approved for exchanging patient data and other sensitive
> information with NHSmail and GSi recipients
> NHSmail provides an email address for your career in the NHS and can be
> accessed anywhere
> For more information and to find out how you can switch, visit
> www.connectingforhealth.nhs.uk/nhsmail
>
>
****************************************************************************
****************************************
>
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>
>

_______________________________________________
openEHR-technical mailing list
openEHR-technical at openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical

 


****************************************************************************
****************************************

This message may contain confidential information. If you are not the
intended recipient please inform the
sender that you have received the message in error before deleting it.
Please do not disclose, copy or distribute information in this e-mail or
take any action in reliance on its contents:
to do so is strictly prohibited and may be unlawful.

Thank you for your co-operation.

NHSmail is the secure email and directory service available for all NHS
staff in England and Scotland
NHSmail is approved for exchanging patient data and other sensitive
information with NHSmail and GSi recipients
NHSmail provides an email address for your career in the NHS and can be
accessed anywhere
For more information and to find out how you can switch, visit
www.connectingforhealth.nhs.uk/nhsmail

****************************************************************************
****************************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20111010/e6a85c6d/attachment.html>

Reply via email to