Stream: dotnet
Topic: disable conformance call
Nils Steinmeyer (Apr 03 2019 at 12:41):
Hello everyone,
while working with the official .NET API for HL7 FHIR i have got a problem regarding with the conformance call.
Actually i want to send a search-request to the administration endpoint of the vonk
(We need to validate if a StructureDefinition is available or not).
As I have seen in wireshark there is also a conformance call to the administration endpoint and the administration endpoint
can't handle that call.
After consultation with my work colleague Simone Heckmann, the following question arises:
Is it possible to disable the conformance call or are there other ways to validate if a StructureDefinition exists or not?
thank you very much!
greetings
Nils Steinmeyer, B.Sc.
IT-Infrastruktur und Services
DMI GmbH & Co. KG
Otto-Hahn-Str. 11-13
48161 Münster
Germany
Simone Heckmann (Apr 03 2019 at 13:05):
I think there is a general question of if and how we can use the dotnet client library to talk to the VONK administration endpoint? I was thinking about redirecting calls to http://my-vonk-server.org/administration/metadata to http://my-vonk-server.org/metadata but this doesn't make much sense, since the admin endpoint doesn't have the same capabilities as the data endpoint. Should Vonk serve a separate CapabilityStatement on the administration endpoint? It would certainly be the correct solution, however it feels a bit overkill since this is not a public endpoint and even our use case needs this kind of access for internal purposes only. Would be nice, if there was a way to tell the client to simply skip checking the CapabilityStatement, if that's possible...
Michel Rutten (Apr 03 2019 at 13:54):
Hi @Simone Heckmann, the .NET BaseFhirClient has a VerifyFhirVersion property. If enabled, the client verifies the server CapabilityStatement on the first request. Default value is false however, so this shouldn't block requests?
Simone Heckmann (Apr 03 2019 at 13:57):
Strange. @Nils Steinmeyer , can you provide details of your error?
Nils Steinmeyer (Apr 04 2019 at 06:27):
Yes of course @Simone Heckmann . I was initializing a FhirClient (API/adiministation).
Next i used the following call _fhirClient.Search<StructureDefinition>("url = http://someUrl")
As result i've got following error message:
[WARNING] Argument is not supported (at /metadata).
at Hl7.Fhir.Rest.TaskExtensions.WaitResult[T](Task1 task)
As I saw in Wireshark the first package is http://API/administration/metadata?_summary=true
The result is the above-mentioned error.
Nils Steinmeyer (Apr 04 2019 at 07:19):
@Michel Rutten thank you for your input. The VerifyFhirVersion was set by default to true.
I changed the VerifyFhirVersion property to false. Now it works. Thank you a lot!
Michel Rutten (Apr 04 2019 at 08:02):
No problem! Our server developers confirmed that the Vonk administration endpoint indeed does not provide a (separate) Capabilitystatement. Just make sure that you disable the BaseFhirClient.VerifyFhirVersion property.
Cheers, Michel
Brian Postlethwaite (Apr 04 2019 at 09:30):
Whoops ;)
Michel Rutten (Apr 04 2019 at 11:33):
@Brian Postlethwaite not an oversight, but hard to implement - think about it...
Simone Heckmann (Apr 04 2019 at 12:26):
...and hardly necessary from an interoperability/conformance viewpoint. You wouldn't want 3rd party apps to mess with your admin database, so I wouldn't consider it a "public FHIR endpoint".
However, people writing administration UIs for VONK may still want to use the dotnet client library, so having a workaround seems legit...
Michel Rutten (Apr 04 2019 at 13:43):
Yes, and the workaround is explicitly disabling VerifyFhirVersion property.
Brian Postlethwaite (Apr 04 2019 at 21:45):
Which is super simple. There's also a constructor flag for that too.
Last updated: Apr 12 2022 at 19:14 UTC
