ok thanks Grahame
On 17/04/2013, at 8:06 AM, "Heather Leslie" <heather.leslie at oceaninformatics.com> wrote: > Hi Grahame, > > The Complications data element is a DV_Text. So it can capture narrative > text. It also has a 0..* Links available as a RM attribute, and so it could > be used to Link to a formal recording of a Problem or Diagnosis using the > specific Problem/Diagnosis archetype, such that it could be added to a > Problem List etc if the clinician thought it warranted it. > > From CKM, Link attributes: ?A Link may be made between any two nodes in an > EHR. Multiple links can be made and the meaning and type of link defined for > each. For example, Links can be used to to associate elements of a Care Plan; > to link a supporting Observation to a Diagnosis; or to link a Procedure and > the Diagnosis recording a complication. > PDF UML > > Heather > > From: openEHR-clinical [mailto:openehr-clinical-bounces at lists.openehr.org] > On Behalf Of Grahame Grieve > Sent: Tuesday, 16 April 2013 12:30 PM > To: For openEHR clinical discussions > Subject: Complications in an event > > If you are recording an event - perhaps a procedure - and you have > complications to record, are these problem/diagnoses? the existing archetypes > simply have complications : text (maybe coded). But aren't these problems, > just problems that may only have existed in the context of an event? > So you could actually use problem/diagnosis? > > Grahame > > > -- > ----- > http://www.healthintersections.com.au / grahame at healthintersections.com.au > / +61 411 867 065 > _______________________________________________ > openEHR-clinical mailing list > openEHR-clinical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-clinical_lists.openehr.org/attachments/20130417/341a50a0/attachment.html>
