Stream: implementers
Topic: Forge my server
Gaute Brakstad (Jul 20 2017 at 12:59):
What fields in conformance are required for forge to connect to a server? @Michel Rutten
Gaute Brakstad (Jul 20 2017 at 13:04):
Forget it i figured it out. Apperently an error in my conformance as it works perfect as soon as you turn off validation of the conformance option.
Michel Rutten (Jul 20 2017 at 13:13):
Hi @Gaute Brakstad, when Forge connects to a FHIR server, it tries to fetch and verify the server's CapabilityStatement. First, the FHIR .NET API verifies that the library version is compatible to the server FHIR version. Forge then inspects the CapabilityStatement.rest property and scans for a list item with .mode = "Server". Then, if found, Forge inspects the .resource property of the found rest component and scans for the value StructureDefinition. In other words, the target system should identify itself as a FHIR server that supports StructureDefinition resources.
If both checks succeed, Forge will continue connecting.
Gaute Brakstad (Jul 20 2017 at 13:22):
Basicly now it works if i turn off option "Verify Server Conformance". Ill run validation on my conformance and see whats the issue.
Michel Rutten (Jul 20 2017 at 13:25):
Hi @Gaute Brakstad, please note that an empty CapabilityStatement is valid according to FHIR spec - but Forge will not accept this (unless you disable the application option).
We've made server the conformance checks configurable to allow you connect to a (development) FHIR server with an improper capability statement.
Last updated: Apr 12 2022 at 19:14 UTC
