Home (Katie Reynolds, Epic)

[ig-feedback]

ch.fhir.ig.ch-core#5.0.0-ballot /

The scope of the CH core specification is limited to profiles, extensions and terminology. One of the core features of FHIR, however, is the native RESTful exchange mechanism. We suggest that CH Core should also contain guidance for the RESTful use of the various resources, for example with the use of the SMART on FHIR mechanisms.

Katie Reynolds, Epic

[katie-reynolds]

More feedback from Epic here in the comments.

On Profiles:
The CH core specification makes the distinction between core profiles and the ones specifically meant to support the document-based EPR. While the EPR profiles are mostly compatible with the international IPS profiles, we suggest that the core profiles should be compatible with the IPA (https://build.fhir.org/ig/HL7/fhir-ipa/branches/pub-update-STU1/toc.html). We've done a comparison using the HL7 FHIR validator (https://confluence.hl7.org/display/FHIR/Using+the+FHIR+Validator#UsingtheFHIRValidator-ComparingProfiles) between the CH Core profiles and the IPA profiles, which already show high level of compatibility. We're happy to share the results (although the file is too large to attach here). Formally declaring a dependency on IPA will also automatically provide base RESTful support for the core specification (see comment on scope).

[katie-reynolds]

On Guidance:

It is not clear what the expectations are for the different participants in the exchange of FHIR resources. We suggest that CH Core (or a companion specification for this purpose) use the new formal descriptions of capabilities per actor to provide the necessary guidance for FHIR servers and clients used in different settings. For examples, please see the IPA profile.

[katie-reynolds]

On Home:
The CH Core specification describes the relationship to the Swiss EPR, which implies that only a document-based exchange is expected to be supported. If other exchange mechanisms are expected to be supported, we suggest that this is made clear (see previous comments as well).

[ziegm]

Added to the changelog as open issue/feature request for the next version.

[ziegm]

23.10.24: FHIR telco: informed about adding to the changelog as open issue/feature