Registration, clinical workflows & guidelines and reporting standards in Haiti

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