Open BenjaminRCope opened 1 year ago
Previously, metadata.service.js generated the operation.definition element as a reference. This is consistent with FHIR v3 standards as shown here:
This causes validation of the generated CapabilityStatement to fail against clients (like HAPI) that check for FHIR compliance.
However, by FHIR v4 standards, operation.definition should now be generated as a canonical, as shown here:
This change rectifies that difference while keeping the original functionality intact.
Previously, metadata.service.js generated the operation.definition element as a reference. This is consistent with FHIR v3 standards as shown here:
This causes validation of the generated CapabilityStatement to fail against clients (like HAPI) that check for FHIR compliance.
However, by FHIR v4 standards, operation.definition should now be generated as a canonical, as shown here:
This change rectifies that difference while keeping the original functionality intact.