Hi Pablo, My understanding is that the purpose of the INSTRUCTION.narrative attribute is to carry a single 'human-friendly' version of what might be a very complex structured set of activities. The best example would be a complex medication order compromising multiple activities, each with a number of structured content. The idea of the 'narrative' attribute is that the key clinical content IS replicated for human consumption. In the work we are currently doing in the UK on medication orders we are concatenating the structured Medication name, dose and frequency to populate the narrative attribute. This makes good clinical sense for safety reasons, particularly when complex timings are involved but for a simple referral this is probably a bit over the top.
I would just replicate the content of the 'Reason for request' in the narrative attribute, unless you know that critical information will be carried in the Reason description, in which case I would concatenate the Reason + Description. Ian On 29 October 2013 02:50, pablo pazos <pazospablo at hotmail.com> wrote: > Hi, I'm reviewing archetypes for a project. Looking at referral request > archetype on the CKM, there are some nodes (Reason for request & Reason > description) that seems to match the semantics of INSTRUCTION.narrative > property. > > Using that archetype to generate the UI in EHRGen, the overlaping was clear > (I though if a doctor records the reason, he/she will have no information to > record on narrative). The problem is that narrative is mandatory on the IM, > and I doubt what to do in cases like this one. > > See the generated UI here: http://tinypic.com/r/ml5og5/5 > > > Is there a real overlaping from the clinical point of view? > > If an archetype has nodes that represents the same semantics as narrative > instruction, is there a need to record narrative anyway? (Even though the > narrative is mandatory by the IM) > > Thanks! > > -- > Kind regards, > Eng. Pablo Pazos Guti?rrez > http://cabolabs.com > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org -- Dr Ian McNicoll office +44 (0)1536 414 994 fax +44 (0)1536 516317 mobile +44 (0)775 209 7859 skype ianmcnicoll ian.mcnicoll at oceaninformatics.com Clinical Modelling Consultant, Ocean Informatics, UK Director openEHR Foundation www.openehr.org/knowledge Honorary Senior Research Associate, CHIME, UCL SCIMP Working Group, NHS Scotland BCS Primary Health Care www.phcsg.org
