visit note encounterDiagnoses

npiaget · January 17, 2020, 11:53am

Hello,

I have a question regarding the tag encounterDiagnoses. I wanted to customize the visit notes to allow for only a given set of diagnosis. So I defined the tag as following:

<encounterDiagnoses required="true" selectedDiagnosesTarget="#encounter-diagnoses-target" diagnosisSets="160182"/>

The concept Dental diagnoses (ID 160182) contained in ICPC diagnosis categories (ID 160167)

However the search box still returns the defaults values, as if diagnosisSets="160182" as no influence. Am I missing something ?

Thanks,

Nicolas

dkayiwa · January 30, 2020, 11:51am

Can you share a screenshot of what you are seeing?

npiaget · January 30, 2020, 3:32pm

Hi Daniel, Thanks for your help, here is the screenshot:

and the code:

<div id="data-collection">

    <encounterDiagnoses required="true" selectedDiagnosesTarget="#encounter-diagnoses-target" diagnosisSets="160182"/>

    <p>
        <label><uimessage code="coreapps.consult.freeTextComments"/></label>
        <obs conceptId="CIEL:162169" style="textarea" rows="5"/>
    </p>

</div>

<div id="encounter-diagnoses-target">
</div>

My assumption was that setting diagnosisSets="160182" would limit the possible answers to the scope of the 160182 Concept set. Is this assumption correct ?

dkayiwa · January 31, 2020, 9:38am

Are you sure that your form did not get overwritten with the default one?

npiaget · January 31, 2020, 11:34am

Yes, I have added a small sentence before the encounterDiagnoses tag:

    Hey, this is my own form.
    <encounterDiagnoses required="true" selectedDiagnosesTarget="#encounter-diagnoses-target" diagnosisSets="160182"/>

    <p>
        
        <label><uimessage code="coreapps.consult.freeTextComments"/></label>
        <obs conceptId="CIEL:162169" style="textarea" rows="5"/>
    </p>

</div>

and the resulting screenshot:

dkayiwa · January 31, 2020, 12:28pm

Which version of the reference application are you running?

npiaget · January 31, 2020, 1:40pm

The reference application version is :2.9.0

The platform: 2.1.4

mksd · February 1, 2020, 7:09am

Hi @npiaget how did you edit that form? I’d have to dig in to be reminded of the exact mechanism, but as far as I remember those forms shipped as resources of the Ref App module can’t really be edited. Whatever you do, in the end it’s always that original resource that shows up.

Do you have a customisation module in your distribution? If yes you’ll easily be able to disable the original visit note form and replace it with yours with some code in that module.

If not, then we’ll have to look deeper at what blocks the edition of those forms and maybe do some work to undo this mechanism.

@mogoodrich I remember you writing something recently about forms as resources vs forms saved in database, but I can’t find it anymore…

npiaget · February 3, 2020, 11:12am

Hi @mksd, thanks for your help.

I did not edit the form shipped with the Ref App module. But instead copied its html code into a new one and added it through the Configure Metadata > Manage Forms administration page.

It seems that my form is really the one that I have created:

mksd · February 3, 2020, 11:15am

Did you give it a new UUID or did you keep c75f120a-04ec-11e3-8780-2b40bef9a44b?

<htmlform formUuid="c75f120a-04ec-11e3-8780-2b40bef9a44b"...

npiaget · February 3, 2020, 11:34am

I gave it another UUID:

<htmlform formUuid="6ec051dd-75aa-4f72-8dce-3e88db889dd5"

dkayiwa · February 3, 2020, 12:47pm

Is this something that you can reproduce here? https://qa-refapp.openmrs.org/

mogoodrich · February 3, 2020, 2:02pm

Is 160182 a primary key or a mapping code? I would try referencing either by uuid or by source/mapping pair (ie CIEL:123456).

npiaget · February 3, 2020, 2:17pm

@dkayiwa, It is working properly on https://qa-refapp.openmrs.org/

Thanks @mogoodrich for the suggestion. However, using either the primary key, the uuid or the source/mapping pair does not work on my version.

Is then my understanding correct that upgrading HTML Form Entry from 3.8.0 to 3.9.2 might solve the problem ?

mksd · February 3, 2020, 8:53pm

Looks like it, did you try on your instance?

npiaget · February 6, 2020, 4:08pm

Sorry for the late reply.

I have upgraded HTML Form Entry to 3.9.2 but it does not change the behavior. Here is a list of the installed modules:

Module's list

OpenHMIS Inventory Module	3.0.0
Atlas Module	2.2
Form Entry App Module	1.4.2
Metadata Sharing	1.5.0
Reporting	1.17.0
ID Generation	4.5.0
EMR API Module	1.27.0
Allergy UI Module	1.8.1
Registration App Module	1.13.0
OpenHMIS Cashier Module	4.0.0
HTML Form Entry UI Framework Integration Module	1.9.0
App Framework Module	2.13.0
Reporting REST	1.10.0
Reference Metadata Module	2.9.0
Metadata Mapping	1.3.4
Admin UI Module	1.2.4
OpenMRS UI Framework	3.15.0
Metadata Deploy	1.11.0
Reference Application Module	2.9.0
App UI Module	1.9.0
Reporting Compatibility	2.0.6
HTML Widgets	1.10.0
Serialization Xstream	0.2.14
Address Hierarchy	2.11.0
Registration Core Module	1.8.0
Attachments	2.1.0
OpenHMIS Backbone Forms Module	3.0.0
Core Apps Module	1.21.0
Event Module	2.7.0
Jasper Reports Module	2.0.0
Chart Search Module	2.1.0 Not Started
Provider Management Module	2.10.0
Calculation	1.2
OpenHMIS Commons Module	4.0.0
Appointment Scheduling UI Module	1.7.0
Open Web Apps Module	1.10.0
FHIR Module	1.18.0
HTML Form Entry	3.9.2
UI Commons Module	2.6.1
Reporting UI Module	1.6.0
Appointment Scheduling Module	1.10.0
Rest Web Services OMOD	2.24.0.573609
Legacy UI Module	1.5.0
Data Exchange Module	1.3.3
UI Library Module	2.0.6
Reference Demo Data Module	1.4.4

Is there anything that can be done beside upgrading to a newer OpenMRS release ? Thanks

dkayiwa · February 6, 2020, 5:10pm

Can you try the same module versions as here? https://uat-refapp.openmrs.org/openmrs/admin/modules/module.list

npiaget · February 7, 2020, 4:16pm

Thanks @dkayiwa it worked!

Just for the record here is the list of module that I’m currently using on top of OpenMRS Version 2.1.4:

Modules

Atlas Module	2.2
OpenHMIS Inventory Module	3.0.0
Form Entry App Module	1.4.2
Reporting	1.19.0
Metadata Sharing	1.6.0
ID Generation	4.5.0
EMR API Module	1.28.0
Allergy UI Module	1.8.2 Not Started
Registration App Module	1.15.0
OpenHMIS Cashier Module	4.0.0
HTML Form Entry UI Framework Integration Module	1.10.0
App Framework Module	2.14.0
Reporting REST	1.10.0
Reference Metadata Module	2.10.1
Metadata Mapping	1.3.4
Admin UI Module	1.3.0
Reference Application Module	2.10.0-SNAPSHOT
OpenMRS UI Framework	3.16.0
App UI Module	1.11.0
Metadata Deploy	1.11.0
Reporting Compatibility	2.0.6
HTML Widgets	1.10.0
Serialization Xstream	0.2.14
Address Hierarchy	2.11.0
Registration Core Module	1.9.0
Attachments	2.2.0 Not Started
OpenHMIS Backbone Forms Module	3.0.0
Core Apps Module	1.26.0
Event Module	2.7.0
Jasper Reports Module	2.0.0
Chart Search Module	2.1.0
Provider Management Module	2.10.0
Calculation	1.2
OpenHMIS Commons Module	4.0.0
Appointment Scheduling UI Module	1.9.0 Not Started
Open Web Apps Module	1.10.0
FHIR Module	1.19.0
HTML Form Entry	3.9.2
UI Commons Module	2.11.0
Reporting UI Module	1.6.0 Not Started
Rest Web Services OMOD	2.26.0.6948bb
Appointment Scheduling Module	1.12.0
Legacy UI Module	1.6.0
Data Exchange Module	1.3.3
UI Library Module	2.0.6
Reference Demo Data Module	1.4.5