Re: Mandatory fields in service_request.v1

2019-05-30 Thread Dileep V S
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 PM Ian McNicoll  wrote:

> '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 good example.
>
> I believe there is a CR to make timing optional - for now I just put in
> some kind of dummy timing structure to get around the mandation.
>
> Ian
>
> Dr Ian McNicoll
> mobile +44 (0)775 209 7859
> office +44 (0)1536 414994
> skype: ianmcnicoll
> email: i...@freshehr.com
> twitter: @ianmcnicoll
>
>
>
> Director, freshEHR Clinical Informatics Ltd.
> CCIO inidus Ltd. i...@inidus.com
> Co-Chair, openEHR Foundation ian.mcnic...@openehr.org
> Hon. Senior Research Associate, CHIME, UCL
>
>
> On Thu, 30 May 2019 at 12:44, Dileep V S  wrote:
>
>> 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 expects. It
>> takes any text value, but I am not sure what to put there.
>>
>> 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
>> ___
>> openEHR-clinical mailing list
>> openEHR-clinical@lists.openehr.org
>>
>> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
>>
> ___
> openEHR-clinical mailing list
> openEHR-clinical@lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
>
___
openEHR-clinical mailing list
openEHR-clinical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org


Re: Mandatory fields in service_request.v1

2019-05-30 Thread Ian McNicoll
'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
good example.

I believe there is a CR to make timing optional - for now I just put in
some kind of dummy timing structure to get around the mandation.

Ian

Dr Ian McNicoll
mobile +44 (0)775 209 7859
office +44 (0)1536 414994
skype: ianmcnicoll
email: i...@freshehr.com
twitter: @ianmcnicoll



Director, freshEHR Clinical Informatics Ltd.
CCIO inidus Ltd. i...@inidus.com
Co-Chair, openEHR Foundation ian.mcnic...@openehr.org
Hon. Senior Research Associate, CHIME, UCL


On Thu, 30 May 2019 at 12:44, Dileep V S  wrote:

> 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 expects. It
> takes any text value, but I am not sure what to put there.
>
> 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
> ___
> openEHR-clinical mailing list
> openEHR-clinical@lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
>
___
openEHR-clinical mailing list
openEHR-clinical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org


Mandatory fields in service_request.v1

2019-05-30 Thread Dileep V S
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 expects. It
takes any text value, but I am not sure what to put there.

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
___
openEHR-clinical mailing list
openEHR-clinical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org