Order Entry UI Sprint 4 Announcement

[darius (Darius Jazayeri)]

@larrystone

Please help curate and make the ticket ready for work so that I can share what I currently have. Thanks

[METAREPO-14] - OpenMRS Issues

I did that, and I moved it to the RA project. FYI it’s probably better to ask what JIRA project to use rather than picking one just because its name sounds right. Metadata Repository is actually for this discontinued project.

@larrystone

I see the challenge now. The current reference metadata repository is using version api-1.7 of the metadatadeploy module whereas the link above is for api-1.10. I will try updating the pom file to use this

Yes, this is the problem, and you are on the right track to fixing it.

Just note that “1.7” is the version of the metadatadeploy module that is being used by the referencemetadata module, and this should be updated to use the latest release, which according to github is “1.10.0”.

Whereas “api-1.10” refers to the maven submodule that is activated only when openmrs-core 1.10+ is running (in this case the “api” submodule supports openmrs-core 1.9.4+, i.e. earlier versions).

So, don’t get mixed up with the two different things you see that look like 1.10.

Just to point you to the right direction, I believe you will need to do two things:

1. update to use the latest metadatadeploy version
2. add a dependency on api-1.10, alongside the dependency on api

[larrystone (Lanre Lawal)]

@darius

Just to point you to the right direction, I believe you will need to do two things:

update to use the latest metadatadeploy version add a dependency on api-1.10, alongside the dependency on api

Thanks @darius. I am currently unable to get point 2 to work. Here’s what I have done

	<dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>org.openmrs.api</groupId>
                <artifactId>openmrs-api</artifactId>
                <version>${openMRSVersion}</version>
                <scope>provided</scope>
            </dependency>
            <dependency>
                <groupId>org.openmrs.api</groupId>
                <artifactId>openmrs-api</artifactId>
                <version>${openMRSVersion}</version>
                <type>test-jar</type>
                <scope>test</scope>
            </dependency>
	        <dependency>
		        <groupId>org.openmrs.module</groupId>
		        <artifactId>reporting-api-2.0</artifactId>
		        <version>${reportingVersion}</version>
		        <scope>provided</scope>
	        </dependency>
            <dependency>
                <groupId>org.openmrs.api-1.10</groupId>
                <artifactId>openmrs-api-1.10</artifactId>
                <version>${openMRSVersion}</version>
                <scope>provided</scope>
            </dependency>
            <dependency>
                <groupId>org.openmrs.api-1.10</groupId>
                <artifactId>openmrs-api-1.10</artifactId>
                <version>${openMRSVersion}</version>
                <type>test-jar</type>
                <scope>test</scope>
            </dependency>
        </dependencies>
    </dependencyManagement>

However, I still couldn’t access the api-1.10 library

Furthermore, after building the omod and uploading to the refApp standalone, it couldn’t start the module, I got an error stating that metadatadeploy version 1.10 is needed. I have metadatadeploy v1.9.0 so I tried checking for upgrade but none was found.

[mogoodrich (Mark Goodrich)]

Hello all… we’ve got the Order Entry OWA incorporated into our PIH EMR pipeline… we set up an “encounter role” last week so that the OWA would work, but after some commits to the OWA yestserday we are seeing the “Configuration for encounterRole is incomplete” message again even though we have the encounter role configured.

I can look into what is happening, but I wanted to confirm that this should be working now, correct? (Getting Order Entry into an OpenMRS build pipeline for testing would be a huge help so I could just compare what we are seeing against that).

Take care, Mark

[mogoodrich (Mark Goodrich)]

Whoops, should have read through my email first…

Sounds like this should be working based on the comments on this ticket… I will follow up here:

OEUI-100

Take care, Mark

[mogoodrich (Mark Goodrich)]

(But I definitely still think that getting it into the OpenMRS build pipeline would be a good idea so we don’t have to ask every time!)

[fred (Fredrick Mgbeoma)]

Hi @harisu

I’m having some challenge testing out the functionality you implemented to sort orders in ascending or descending order.

Here is what I have done:

• Removed the existing Rest Web Services omod

• Uploaded and started the new Rest Web Services omod

• Restart the server

• Change the request URL to include the sort parameter as indicated here - /order?sort=desc&totalCount=true&limit=${limit}&startIndex=${startIndex}&careSetting=${careSetting}&patient=${patientUuid}&status=inactive&t=drugorder&v=full

Following the steps above does not have any change in the way orders are fetched.

I’m I missing any steps?

How do I get it to work as expected?

Moved this conversation from this Talk post so every discussion is in the same place.

cc: @dkayiwa @flavia @larrystone @betty @zeze @geofrocker @kodero @mogoodrich

[harisu (harisu fanyui)]

The request URL is correct and typically that is what i was to impliment. Here is the commit with the changes i made from which the omod was generated, https://github.com/fanyui/openmrs-module-webservices.rest/commit/0cfe43f67924dcf6cfb157f6ac0ef04d0753c01f

My bad for the inconvinience couldn’t properly test it because of the javacript errors. on the formEntry app i installed.

I need some help debugging it.

cc @larrystone @fred @betty @flavia @betty @zeze @geofrocker @kodero @mogoodrich @dkayiwa

[fred (Fredrick Mgbeoma)]

What progress have you made so far, if any?

Where exactly are you stuck?

Kindly add screenshots as it would be very helpful .

[harisu (harisu fanyui)]

From the previous discurssion on talk. I couldn’t create and order to test the changes since i had no orders to test on. the save button becomes blured. i got this error.

[fred (Fredrick Mgbeoma)]

Kindly update your local OWA with the most recent changes from master branch. Then attempt to create a drug order using the free text tab.

Reply with your update.

[larrystone (Lanre Lawal)]

@harisu Better still you can test online here. Use doctor/Doctor123 as username/password

[larrystone (Lanre Lawal)]

Hi @darius @dkayiwa I have a PR up to show how far I have gone with the ticket. Please find time to look into it. Thanks

RA-1498: include best-practice order frequencies out of the box

[dkayiwa (Daniel Kayiwa)]

@larrystone did you first of all compile, install, and test to confirm it is working as intended?

[larrystone (Lanre Lawal)]

Yes I did. I have also uploaded the omod to the ticket for further testing

[darius (Darius Jazayeri)]

@larrystone, you need to make a change something like this:

$ git diff
diff --git a/pom.xml b/pom.xml
index 775bce7..8b04e54 100644
--- a/pom.xml
+++ b/pom.xml
@@ -27,7 +27,7 @@
        <metadatasharingVersion>1.2.2</metadatasharingVersion>
         <metadatamappingVersion>1.2.1</metadatamappingVersion>
        <dataexchangeVersion>1.3.2</dataexchangeVersion>
-       <metadatadeployVersion>1.7</metadatadeployVersion>
+       <metadatadeployVersion>1.10.0</metadatadeployVersion>
        <eventVersion>2.5</eventVersion>
        <providermanagementVersion>2.5.0</providermanagementVersion>
        <reportingVersion>0.10.6</reportingVersion>
@@ -131,6 +131,12 @@
                 <version>${metadatadeployVersion}</version>
                 <scope>provided</scope>
             </dependency>
+                       <dependency>
+                               <groupId>org.openmrs.module</groupId>
+                               <artifactId>metadatadeploy-api-1.10</artifactId>
+                               <version>${metadatadeployVersion}</version>
+                               <scope>provided</scope>
+                       </dependency>
             <dependency>
                 <groupId>org.openmrs.module</groupId>
                 <artifactId>metadatamapping-api</artifactId>

I see two mistakes in what I think you were trying:

1. you were adding openmrs-api-1.10, but this is wrong. You want metadatadeploy-api-1.10, i.e. you want the part of metadatadeploy that runs against openmrs 1.10+.
2. you put things in dependencyManagement instead of dependencies. (This is non-obvious, but dependencyManagement allows you to specify scopes and versions for dependencies that may be included in multiple pom.xml files, but doesn’t actually include them itself.)

[larrystone (Lanre Lawal)]

Thanks for your valuable feedback @darius, I will work with these and update you and the PR accordingly

[larrystone (Lanre Lawal)]

I have a challenge about to represent the orderFrequency for an order described as ONCE. I guess ONCE here means once in a lifetime. My concern is how to represent this as a fraction of frequencyPerDay. Any suggestions? cc @darius @dkayiwa @wyclif @kodero

[harisu (harisu fanyui)]

@fred. i’ve done as you proposed and i still get this.

I also notice the application of a class illegalValue to the unit imput field when i inspect the element

.

@larrystone The credentials you gave i logged in with and could not create an order patient id ac5b7f58-a1d6-4f0d-b7df-5ec24ed8bbad

[wyclif (Wyclif Luyima)]

@larrystone

I have a challenge about to represent the orderFrequency for an order described as ONCE. I guess ONCE here means once in a lifetime. My concern is how to represent this as a fraction of frequencyPerDay. Any suggestions?

Once means take the dose one time and the drug order is technically expired after, you can take it again in the future in case of a new prescription, therefore the frequencyPerDay value would be 1

[larrystone (Lanre Lawal)]

Thanks for pointing this out @wyclif.