Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add new FhirContactPoints domain. #253

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

mherman22
Copy link

No description provided.

@mherman22 mherman22 changed the title Add Domain for FhirContactPoints Add new FhirContactPoints domain. Oct 20, 2023
return locationService.getLocationAttributeTypeByUuid(attributeType);
break;
case PROVIDER:
baseAttributeType = providerService.getProviderAttributeTypeByName(attributeType);
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i guess we need to backport this commit (that introduces the getProviderAttributeTypeByName() method) to the 2.5.x branch curently at 5.13.0-SNAPSHOT branch.

cc: @ibacher

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmmm... let's just target this at 2.6+ then. I think that's less confusing.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome,lemi update that

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done!

import static org.hamcrest.Matchers.equalTo;
import static org.hamcrest.Matchers.is;

public class FhirPatientContactPointMapIntegrationTest extends DomainBaseModuleContextSensitiveTest {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this test needs to be in the api-2.5 (probably api-2.6) submodule or something.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done!

@ibacher
Copy link
Member

ibacher commented Oct 30, 2023

@mherman22 Is there no way to get this to work without shifting to 2.0.0 of the FHIR2 module? I would prefer to support older versions.

@mherman22
Copy link
Author

@mherman22 Is there no way to get this to work without shifting to 2.0.0 of the FHIR2 module? I would prefer to support older versions.

I was trying this out. I'm pushing it back to 1.11.0 however the challenge there has to do with the location type translator not being got as a bean i.e NoSuchBeanException

@ibacher
Copy link
Member

ibacher commented Nov 15, 2023

It looks like we're going to need to make 2.6 the minimum version for the LoaderTest and probably the validator too for this to work. @Ruhanga Do you have an opinion on that? Otherwise, we maybe add something to the Loader to not try to run a domain if a valid version of a loader isn't available.

@mherman22
Copy link
Author

It looks like we're going to need to make 2.6 the minimum version for the LoaderTest and probably the validator too for this to work. @Ruhanga Do you have an opinion on that? Otherwise, we maybe add something to the Loader to not try to run a domain if a valid version of a loader isn't available.

Fyi, I have done this locally though it is now not loading the loader for QUEUE so I am still looking for a workaround around that.

@Ruhanga
Copy link
Member

Ruhanga commented Nov 16, 2023

It looks like we're going to need to make 2.6 the minimum version for the LoaderTest and probably the validator too for this to work.

@ibacher, @mherman22 concerning the above, upgrading to OpenMRS Core greater than 2.4.0 might require refactoring on the part of the Validator to accommodate new changes + upgraded libraries on Core. This will consequently need some extensive testing of the Validator itself.

@ibacher
Copy link
Member

ibacher commented Nov 27, 2023

First bit looks like we need to change the calls like:

executeChangelog("changelog", null);

To:

executeChangelog("changelog", (ChangeSetExecutorCallback) null);

In ConfigTester...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants