Testing new Migration of Encounter Diagnosis feature

Tags: #<Tag:0x00007f3021a37638>

Hi all,

Extending discussion from Status of Platform 2.2 release process.

Work has been done on TRUNK-5342 and we expect a folk to test out this new feature.

Recommended steps of testing this

  • Run a server with platform version lower than 2.2 and the latest snapshot version of the emrapi module
  • Add Encounter Diagnosis to some Patients
  • Upgrade to platform 2.2. This can be done by just changing the openmrs.war file with the SNAPSHOT one
  • Install/upgrade the/to latest version of the emrapi module
  • From the admin screen, its quite intuitive and easy to do the migration.
  • Then get back to us and tell us what happened.

Please this is urgent coz we expect to start the release process early this week. I will be there to assist who ever is there to test this feature.

Regards

Samuel

1 Like

hei can i take on this with effect from monday??

As for providers/ends users that aren’t developers, here is the latest version of the emrapi.omod and openmrs.war files.

~Samuel

No earlier slot according to your schedule?

the latest is monday because this week am going to be off during the weekend

Hi @samuel34 , trying to install the emrapi module but there is some test failing out while compiling Check https://pastebin.com/DWRd9rdc

Anything am missing?

Are sure thats the latests without any local changes?

Assuming the your upstream ref is ‘https://github.com/openmrs/openmrs-module-emrapi’, while at master hit git reset --hard upstream/master then try again.

But just in favor of time, you could just get it from here

https://www.dropbox.com/s/37uhuk4wq62g2pi/emrapi-1.25.0-SNAPSHOT.omod?dl=0

@samuel34 can you create a ticket for fixing that randomly failing test? Then add an ignore attribute to it? Something like this: https://github.com/openmrs/openmrs-core/blob/master/api/src/test/java/org/openmrs/validator/PersonNameValidatorTest.java#L760

Created at

And committed at https://github.com/openmrs/openmrs-module-emrapi/pull/156. @dkayiwa

@samuel34 , what could be making the platform upgrade hung at the screenshot below?

for quite some hours now.

The platform being upgraded is of version 2.1.3 to version 2.2.0 SNAPSHOT using reffapp 2.8 distro server.

I’m also using the SDK tool

Don’t expect it to redirect itself automatically after the upgrade. Actually the upgrade process isn’t well defined. what happens when you try accessing this url now.

localhost:8086/openmrs/login.htm

It may have finished but possibly not updated the UI. Just stop openmrs and run it again.

Thanks @samuel34 and @dkayiwa

I however arrive at this UI framework error (https://pastebin.com/w815K0E9) on trying to access this url.

The error above has persisted for the three attempts to upgrade, even after rerunning openmrs. Just wondering why :thinking:?

Could you provide a full error log?

Full error log = https://pastebin.com/xmepCWMq.

For this error, use the latest snapshot version of the rest webservices module. The same for the emrapi and coreapps modules.

1 Like

Thanks @dkayiwa :slightly_smiling_face:, upgrading rest webservices module to latest snapshot version did resolve the error.

Hi @samuel34 , here are the steps and observations made from testing EMR API module

I ;

-Installed openmrs reffapp 2.8.0-distro (running platform 2.1.3 version)

-Registered some patients with the following sample encounter diagnoses (coded as F32.9, B54 – don’t think it matters the code)

-Upgraded platform version to 2.2.0-SNAPSHOT

-Upgraded webservicesmodule rest module from version 2.21.0 to 2.23.0-SNAPSHOT (to solve the UI error encountered after platform upgrade)

-Verified all the encounter diagnoses recorded earlier with registered patients present

-Upgraded EMR api module from 1.24.6-SNAPSHOT to 1.25.0-SNAPSHOT

-Verified all the encounter diagnoses recorded earlier with registered patients absent (or deleted)

End of test .

Anything missing ?