Stream: IG creation
Topic: Consent2Share(C2S) on FHIR
vladimir matryshov (Jul 14 2020 at 20:21):
Hello, We're having some trouble in upgrading FHIR from DSTU3 to R4 in Consent2Share project.
https://github.com/bhits/consent2share
https://okmis.info/hapi-fhir-jpaserver/
We got the following the issue and not sure how to solve the issue:
Incorrect resource type found, expected "Conformance" but found "CapabilityStatement"
Can you please help this?
Here is error log file. error.log
David Pyke (Jul 14 2020 at 20:32):
Can you give a little more detail on what you mean by "upgrading FHIR"? The Consent2Share project was a DSTU3 FHIR IG, are you upgrading that or upgrading the HAPI server? What are you doing when you get that error?
vladimir matryshov (Jul 14 2020 at 21:54):
Hello, David. Thank you for your response.
Yes. You're correct. The consent2share project was a DSTU3. I was going to upgrade the FHIR version of C2S to R4.
In order to do this, I used hapi-fhir-jpaserver-starter project (https://github.com/hapifhir/hapi-fhir-jpaserver-starter) and I updated some configurations of C2S so that C2S works on the new FHIR(R4).
When I run the provider-ui of C2S to create/update a patient, it calls FHIR REST APIs using fhir client while it calls ums(user management system) of C2S and I got the above error. Please check the error.log file I attached.
David Pyke (Jul 14 2020 at 22:05):
Updating Consent2Share is more than just converting the resources. You're going to have a lot of work to convert the whole IG. The error for the Conformance resource is only the first of many issues that need to be solved as the changes from STU3 to R4 were large and varied. For this error, the Conformance resource was deprecated and replaced with the CapabilityStatement, a completely different resource.
vladimir matryshov (Jul 14 2020 at 22:16):
Yeah, I think so the Conformance resource was deprecated and no longer used in R4.
So I tried to find the source code that is related the Conformance resource and replace it with CapabilityStatement but I couldn't find.
Which part of the C2S should I modify to solve the issue?
David Pyke (Jul 14 2020 at 22:39):
You'll need to create the CapabilityStatement for the R4 version of C2S and then modify the server to hand it out. This is not a small change, you're likely to set a project to do the update of C2S from DSTU3 to R4
vladimir matryshov (Jul 14 2020 at 22:46):
Yeah, I've set the project to do the update of C2S from DSTU3 to R4.
I'm not sure about creating the CapabilityStatement for the R4 version of C2S. Can you tell me about it in detail?
David Pyke (Jul 14 2020 at 22:50):
The base information is here: http://hl7.org/fhir/capabilitystatement.html
vladimir matryshov (Jul 15 2020 at 14:46):
Can you refer a C2S freelancer to assist with the salvage?
David Pyke (Jul 15 2020 at 15:17):
Yes, I can.
Jens Villadsen (Jul 15 2020 at 20:01):
@vladimir matryshov from your log it looks like your server and client are not aligned in what version that should be used. It looks like the client speaks STU3 or R4, while your server speaks DSTU2
Last updated: Apr 12 2022 at 19:14 UTC
