Ian
Ian
Functionally, it's incorrect to assume a patient should only have one name. We can, however, try voiding any names that are not in the list. (The UI defaults to the...
cc: @jayasanka-sack @dkayiwa
I have no idea why the tests are failing here... they pass locally in every way I can figure out how to run them.
@kajambiya As a general rule, the most important thing is that if there is an error and it blocks the user from taking an action, that error must be shown...
I presume we need the Bed Management backend module to make this work too?
We actually support the various name components via [custom extensions](https://github.com/openmrs/openmrs-module-fhir2/blob/3432289ddbb143f0828d3d7b81f9060b5e232767/api/src/main/java/org/openmrs/module/fhir2/api/translators/impl/PersonNameTranslatorImpl.java#L104) rather than standard extensions—the fields we have may, but don't necessarily, align with the semantic meaning of those extensions.
@xprl-gjf Apologies. I made some comments a while ago, but they never got added.
@xprl-gjf Yeah, I can't see this really working well until the backend changes are in, no?
I don't think we're yet at a point where the print feature is ready to be automatically enabled. We can maybe discuss a way to make it possible to enable...
@rbuisson What I really mean is that this is something like the third re-write of how we configure this component and it isn't clear to me that we are following...