FHIR Chat · CapabilityStatemen - profiles not matching annotations

Stream: hapi

Topic: CapabilityStatemen - profiles not matching annotations

Tobias Cervin (Nov 27 2019 at 06:54):

Can't seem to become friends with CapabilityStatement in our HAPI fhir-server/facade. Even though our Providers and Models have custom profile-urls and look like this:

@RegisterProfileClass(profile = CUSTOM_PROFILE_URL, model = EHMMedicationRequest.class)
@ResourceProviderQualifier(MedicationRequestResourceProvider.class)
public class MedicationRequestResourceProvider extends AbstractValidatingProvider<EHMMedicationRequest> implements IFhirResourceProvider<MedicationRequest> { ... }

@ResourceDef(name="MedicationRequest", profile=CUSTOM_PROFILE_URL)
public class EHMMedicationRequest extends MedicationRequest { ... }

The "GET [base]/metadata?mode=full" returns:

{
          "type": "MedicationRequest",
          "profile": "http://hl7.org/fhir/StructureDefinition/MedicationRequest",
          ...
}

I have tried debugging at the start of the application and found that RuntimeSourceDefinition has the correct custom myResourceProfile. Anyone else wrestled with this?

Jens Villadsen (Nov 27 2019 at 21:05):

This was part of https://github.com/jamesagnew/hapi-fhir/pull/1088 . If you run on 4.1.0, it should work for you (as it works for me ;) )

Tobias Cervin (Nov 28 2019 at 14:04):

This was part of https://github.com/jamesagnew/hapi-fhir/pull/1088 . If you run on 4.1.0, it should work for you (as it works for me ;) )

Thanks for reply!

We have bumped up to 4.1.0 but the same issue remains.

Debuging through:

if (nextEntry.getKey().isEmpty() == false) {
        Set<TypeRestfulInteraction> resourceOps = new HashSet<>();
        CapabilityStatementRestResourceComponent resource = rest.addResource();
        String resourceName = nextEntry.getKey();

        RuntimeResourceDefinition def;
        FhirContext context = configuration.getFhirContext();
        if (resourceNameToSharedSupertype.containsKey(resourceName)) {
          def = context.getResourceDefinition(resourceNameToSharedSupertype.get(resourceName));
        } else {
          def = context.getResourceDefinition(resourceName);
        }
        resource.getTypeElement().setValue(def.getName());
        resource.getProfileElement().setValue((def.getResourceProfile(serverBase)));

And the custom profiles are nowhere to be found...

Jens Villadsen (Nov 28 2019 at 20:20):

- just to be sure - we are talking about the need for a server to generate a capabilitystatement where it states that eg. the MedicationRequest is profiled according to what is stated in the @ResourceDef.profile annotation ?

Tobias Cervin (Nov 29 2019 at 06:06):

- just to be sure - we are talking about the need for a server to generate a capabilitystatement where it states that eg. the MedicationRequest is profiled according to what is stated in the @ResourceDef.profile annotation ?

Just so! :slight_smile:

Jens Villadsen (Dec 02 2019 at 13:31):

its hard to say then. It works for us

{
          "type": "Appointment",
          "profile": {
            "reference": "http://ehealth.sundhed.dk/fhir/StructureDefinition/ehealth-appointment"
          }, ...
}