Registration, clinical workflows & guidelines and reporting standards in Haiti

mksd · January 12, 2018, 5:52pm

FYI @ball and @mogoodrich I sent a calendar invite to both of you for Tue Jan 16th @ 10am EST.

mogoodrich · January 16, 2018, 4:38pm

Great meeting… a few follow up items.

You can see how we define localizations for Metadata here:

https://github.com/PIH/openmrs-module-mirebalais/blob/master/api/src/main/resources/messages.properties#L246

I did confirm that most, if not all, of our translations are in our “Mirebalais” module. For metadata declarations that have been moved to the Haiti Core module, we should move the declarations there. I’ve created a ticket reminding us to do this.

For reference, here’s the code in UI Framework that handles localizations:

github.com

openmrs/openmrs-module-uiframework/blob/master/api/src/main/java/org/openmrs/ui/framework/FormatterImpl.java?utf8=✓#L140


      
          		} else {
          			df = UiFrameworkUtil.getDateFormat(administrationService, locale);
          		}
          		return df.format(d);
          	}
          	
          	private boolean hasTimeComponent(Date d) {
          		Calendar cal = Calendar.getInstance();
          		cal.setTime(d);
          		return cal.get(Calendar.HOUR_OF_DAY) != 0 || cal.get(Calendar.MINUTE) != 0 || cal.get(Calendar.SECOND) != 0
          		        || cal.get(Calendar.MILLISECOND) != 0;
          	}
          	
          	private String format(Role role, Locale locale) {
          		String override = getLocalization(locale, "Role", role.getUuid());
          		return override != null ? override : role.getRole();
          	}
          	
          	private String format(OpenmrsMetadata md, Locale locale) {
          		String override = getLocalization(locale, md.getClass().getSimpleName(), md.getUuid());
          		return override != null ? override : messageSource.getMessage(md.getName(), null, locale);

Here’s where we store our concept metadatasharing packages:

Hopefully they will be updated in the next couple days to be 2.x compatible! I am working on that now.

If you haven’t been watching this thread, it’s probably one you’d like to follow:

Looking forward to talking more… it would be useful to get @ddesimone involved in any discussions of our clinical workflow.

Take care, Mark

mksd · January 16, 2018, 6:00pm

Thanks both @ball and @mogoodrich for attending our call and providing such valuable input about your work in Haiti.

Cool, I understand now your approach to localizing metadata names, that’s quite nifty! If we decide to go for reusing PIH Core directly in our Bahmni distro then we would have to expand the implementation of Ext I18N to support your logic. We just gave it a 20 min brainstorm and I think that it would work just fine. But just to be sure, in fact all metadata are saved in some default locale, correct? Presumably ‘fr’ as I can see here for encounter types (and from what Ellen said over the meeting)?

It is well possible that we don’t reuse PIH Core directly in our distro since we have now established this process of setting OpenMRS backend configs via our Initializer module. This enables us to not have any implementation-specific modules anymore, and I believe that we will want to stick to that paradigm by extending the Initializer further. But let’s see…

We will now have a conversation with the key stakeholders at our implementation site in Haiti to outline and prioritise the clinical workflows that they are most interested in. And we will come back to you after that for a follow up call to dig further into PIH/ZL, if that’s ok with you?

Thanks a bunch. So helpful and insightful!

ball · January 16, 2018, 6:53pm

Good conversation and nice to see all your expertise contributing to new projects in Haiti. Let us know about the followup meeting covering clinical workflows.

Ellen