Ken and all,
Not sure who in this community was tasked to investigate the Canadian FHIR registry but I’d like to provide an update on some of the work Infoway has done/is doing to support FHIR implementation. I couldn’t attend the Oct.4 call due to schedule conflict.
Infoway has released Gateway FHIR terminology service on Sept.14, it supports FHIR ValueSet resource read, vread, search, $expand, $validate-code operations to access about 200 pan-Canadian valuesets. The Swagger API documentation and Sandbox can be found
here
With regard to FHIR registries for NamingSystem, identifiers, IGs/profiles/extensions, we’ve been following the movement internationally, especially the FHIR core team.
As part of the Infoway Terminology Gateway release on Sept.14, we have published a “URL Catalog”
“URL Catalog” which is intended to serve as pan Canadian Valuse Set URL registry, it provides canonical URLs to the PCS valuesets, and mapping to it’s name and OID. The catalog can be retrieved via RESTful API as well. Currently any new entries to this catalog has to be provided to Infoway to be published, we’re building a service end point and a process to support external submissions from the community.
There is going to be a webinar next month, during which demos of new Gateway features and FHIR terminology service are provided.
With regard to FHIR registry for IGs, Conformance resources including profiles and extensions. There has been some update internationally, we should pay attention so we don’t reinvent the wheels. As you know
http://hl7.org/fhir/registry/ has not been populated, nor there was a process to support publication submissions of both international and country specific IGs and conformance resource.
The latest update is that
HL7 FHIR Foundation was incorporated in Michigan, U.S. as a not for profit organization independent from HL7, it is positioned as a home for FHIR implementation community, supporting implementation Guide & Best Practices Registries, Forums, Reference implementations, resources for conformance testing. Board members are from various organizations including HL7, vendors. It is going to be a membership based business model, currently a lot of things are being worked on including
- Membership policy and process;
- Business plan and financial sustainability;
- Policy and procedures to hosting FHIR artifacts including FHIR implementation guides, profiles, extensions, etc on fire.org website
- Develop registries and repositories of FHIR artefacts, both international and country specific
It is clear that FHIR Foundation wants to host and publish all FHIR implementation resources, to become the go-to place for FHIR implementers around the world. We should monitor this and leverage what we can, keep this in mind before introducing our own FHIR registry in Canada. The content of the IGs are of course not the responsibility of FHIR Foundation, but rather the submitter.
HL7 FHIR core team provides FHIR Implementation Guide publishing tool(
http://wiki.hl7.org/index.php?title=IG_Publisher_Documentation). This is important not only it’s now separated from the FHIR build tree, the dependencies are cleaned up, also hopefully reduce the variations in the IG artefacts that any registry/publication platform has to deal with.
I invite anyone who is interested in further discussions to get in touch, also invite everyone to join the Infoway Webinar on Gateway FHIR terminology service.
Print
Email
