Re: Mandatory fields in service_request.v1

Thank you regards Dileep V S *Founder* HealtheLife Ventures LLP m: +91 9632888113 a: 106, Innovation Centre, IIIT, Electronics City, Bangalore 560100 w: ehr.network, ayushehr.com e: dil...@healthelife.in On Thu, May 30, 2019 at 5:30

Re: Mandatory fields in service_request.v1

'timing' is intended to carry some sort of parsable timing structure such as GTS http://www.vico.org/HL7_V2_5/v251/hl7v251typGTS.htm but I never use this. GTS is horrible and we have found it much more appropriate to model times inside the archetype - see medication orders/ dose and timings for a

Mandatory fields in service_request.v1

Hi, I am using [openEHR-EHR-INSTRUCTION.service_request.v1] in a template and notice that it has two mandatory nodes - narrative & current_activity:0/timing. Narrative expects a human readable narrative of the request (mandatory for all instructions). But I am not sure what the 'timing' node