Thanks Ian,
I tested and it works. Your detailed explanation was a great help. I am
sure you will make a very good teacher👍. Though Pablo also said the same
thing first, I did not fully get it.
regards
Dileep V S
*Founder*
HealtheLife Ventures LLP
m: +91 9632888113
a: 103, Innovation Centre, IIIT, Electronics City, Bangalore 560100
w: healthelife.in e: dil...@healthelife.in
On Wed, Dec 20, 2017 at 2:03 PM, Ian McNicoll <i...@freshehr.com> wrote:
> Hi Dileep,
>
> As Pablo says, any DV_TEXT can be sub-classed as DV_CODED_TEXT.
>
> How are you storing the composition data ,FLAT JSON?
>
> If so you can save coded data for any DV_TEXT node as follows
>
>
> "adverse_reaction_list/allergies_and_adverse_reactions/adverse_reaction_risk:0/causative_agent|code":
> "91936005",
>
> "adverse_reaction_list/allergies_and_adverse_reactions/adverse_reaction_risk:0/causative_agent|value":
> "allergy to penicillin",
> "adverse_reaction_list/allergies_and_adverse_reactions/adverse_reaction_
> risk:0/causative_agent|terminology": "SNOMED-CT",
>
>
> "adverse_reaction_list/allergies_and_adverse_reactions/adverse_reaction_risk:0/causative_agent":
> "non-coded text",
>
> The fulll RAW JSON equivalent is
>
> {
> "@class": "ELEMENT",
> "name": {
> "@class": "DV_TEXT",
> "value": "Causative agent"
> },
> "archetype_node_id": "at0002",
> "value": {
> "@class": "DV_CODED_TEXT",
> "value": "allergy to penicillin",
> "defining_code": {
> "@class": "CODE_PHRASE",
> "terminology_id": {
> "@class": "TERMINOLOGY_ID",
> "value": "SNOMED-CT"
> },
> "code_string": "91936005"
> }
> }
> },
>
> AQL to retreive is something like
>
> b_a/data[at0001]/items[at0002]/value/value as causative_agent_value,
> b_a/data[at0001]/items[at0002]/value/defining_code/code_string as
> causative_agent_code,
> b_a/data[at0001]/items[at0002]/value/defining_code/terminology_id/value
> as causative_agent_terminology,
>
> Ian
>
> Dr Ian McNicoll
> mobile +44 (0)775 209 7859
> office +44 (0)1536 414994
> skype: ianmcnicoll
> email: i...@freshehr.com
> twitter: @ianmcnicoll
>
>
> Co-Chair, openEHR Foundation ian.mcnic...@openehr.org
> Director, freshEHR Clinical Informatics Ltd.
> Director, HANDIHealth CIC
> Hon. Senior Research Associate, CHIME, UCL
>
> On 20 December 2017 at 05:41, Dileep V S <dil...@healthelife.in> wrote:
>
>> Hi,
>>
>> We are in the process of adding a terminology server to code the
>> composition date. However many of the nodes that can be coded are text
>> fields (Eg. Symptom/sign name in Symptom/sign archetype that we have used
>> in Complaints template). As we understand, the data type has to be changed
>> to CODED-TEXT before we can store coded data.
>>
>> What is the best practice to do this? Shall we go ahead and edit the
>> archetypes, in which case our archetypes will no longer be same as the ones
>> in CKM? Are there more robust mechanisms to achieve this without breaking
>> compliance to CKM?
>>
>> regards
>> Dileep V S
>> *Founder*
>> HealtheLife Ventures LLP
>> m: +91 9632888113 <+91%2096328%2088113>
>> a: 103, Innovation Centre, IIIT, Electronics City, Bangalore 560100
>> w: healthelife.in e: dil...@healthelife.in
>>
>> _______________________________________________
>> openEHR-technical mailing list
>> openEHR-technical@lists.openehr.org
>> http://lists.openehr.org/mailman/listinfo/openehr-technical_
>> lists.openehr.org
>>
>
>
> _______________________________________________
> openEHR-technical mailing list
> openEHR-technical@lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-
> technical_lists.openehr.org
>
_______________________________________________
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
