atural
> language processing is attempting to turn clinical records into
> post-coordinated SNOMED codes. This is interesting work and some form
> of this approach is likely to be helpful in the future. I do not think
> openEHR or CDA are well suited to meet these requirements where
> natural language (and formatted) text is mixed in with structured data
> that can be processed. CDA runs the two in parallel while openEHR
> forces explicit structure where required. The openEHR approach is
> undoubtedly safer but it is worth considering the best approach to
> meet these needs.
>
> 5.Archetypes assume the openEHR reference model. In the current tools
> this is somewhat problematic as designers have to know a little about
> the reference model -- but it is also the most important feature as
> consistency is critical for safe computing. Mistakes were made early
> on in not assuming the reference model features and being explicit
> about some features when there was actually no constraint. We have
> learned about this and the next round of tooling will need make it
> easier for designers and not create constraints where none are required.
>
> The main opportunity for which everyone will be grateful is if we can
> use openEHR archetypes to create consistent CDA and provide the
> transforms required to move seamlessly from CDA to openEHR and back.
> This provides a single source of truth and is what many people are
> seeking. What we need to take this further is:
>
> 1.A standard transformation of a template of an openEHR Composition to
> HL7 CDA -- converting EHR attributes to CDA attributes -- that does
> not require explicit modelling of data that is already captured in the
> openEHR RM. The transformation may require renaming of openEHR RM
> attributes that are specific for that the template as CDA documents
> may have different labels that are the same thing in an EHR system
> (e.g. a prescription may have a 'prescriber' whereas a document may
> have an 'author' where both are the legal creator of the document).
>
> 2.An archetype to CDA transform (and back) that labels the CDA data in
> a way that it is clear which archetype this CDA data conforms to. This
> is needed for each archetype and should be available on CKM.
>
> The openEHR RM should also consider adding a CLUSTER to participation
> to allow structured data or include participation data in the
> composition. Other_participations may be the location for this with
> IDs that are referenced within the composition -- but this is not the
> planned use and will need some consideration. Some may argue that this
> should be from the demographic model but I do not think so.
>
> Thoughts?
>
> Cheers, Sam Heard
>
>
> ___
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
--
Ocean Informatics *Thomas Beale
Chief Technology Officer, Ocean Informatics
<http://www.oceaninformatics.com/>*
Chair Architectural Review Board, /open/EHR Foundation
<http://www.openehr.org/>
Honorary Research Fellow, University College London
<http://www.chime.ucl.ac.uk/>
Chartered IT Professional Fellow, BCS, British Computer Society
<http://www.bcs.org.uk/>
Health IT blog <http://www.wolandscat.net/>
*
*
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110105/4535dd9c/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: ocean_full_small.jpg
Type: image/jpeg
Size: 5828 bytes
Desc: not available
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110105/4535dd9c/attachment.jpg>
