Stream: new zealand
Topic: connectathon
David Hay (Jun 16 2019 at 03:09):
Stream for questions during NZ Connectathon
Chandan Datta (Jun 18 2019 at 21:52):
Is there a HAPI FHIR reference implementation server with the NZ resources+extensions modeled that programmers can look into the code as in today's practical session? If anyone has done a docker or k8s deployment on prem, I will be keen to have a look at. keen to see how an extension can be modeled in conman+clinfhir and Testscripts (https://www.hl7.org/fhir/testscript-example.html) written and tested against a server instance.
Chandan Datta (Jun 18 2019 at 21:52):
If anyone has built a CDA XSLT equivalent with a FHIR docs resource, please let me know if you are happy to share you experience
Chandan Datta (Jun 18 2019 at 22:03):
Is there a swagger API dev portal for any of the reference servers? https://wiki.openmrs.org/display/projects/FHIR+Swagger+Documentation
Chandan Datta (Jun 18 2019 at 22:06):
Also if anyone has tried .net reference implementation server building from code and deployment with docker, keen to have a discussion: https://buildmedia.readthedocs.org/media/pdf/main-site-test/latest/main-site-test.pdf
David Hay (Jun 18 2019 at 22:26):
The various resources (StructureDefinitions) should be on the test server (http://home.clinfhir.com:8054/baseR4/) - you can search for them by querying on the url (you can get that from the logical model). It's still a work in progress though, so are very likely to change! Eventually theywill all be on an official registry
Dan Orr (Jun 18 2019 at 23:25):
Anyone have a working example of calling the $match operation? I'm getting an error about the JSON I'm sending.
Dan Orr (Jun 18 2019 at 23:36):
Anyone have a working example of calling the $match operation? I'm getting an error about the JSON I'm sending.
You have to send a Patient resource. The mimetype also needs to be application/fhir+json OR text.
{ "resourceType": "Patient", "name": [ { "family": [ "Doe" ] } ], "gender": "male", "birthDate": "1987-03-12" }
Chris Daynes (Jun 18 2019 at 23:59):
The value for the family key is not an array
Dan Orr (Jun 19 2019 at 00:07):
Agreed, however, that query was working for me. Given name is more likely to be an array
Lloyd McKenzie (Jun 19 2019 at 01:06):
It's not a question of "more likely". It's a question of which version of FHIR you're using. R4 and on, name is not an array. Prior to that, it is.
David Hay (Jun 19 2019 at 01:07):
yep - given is an array (0..* in the spec) family is a single (0..1) - see http://hl7.org/fhir/datatypes.html#HumanName
Dan Orr (Jun 19 2019 at 02:52):
Ah yes, @Lloyd McKenzie and @David Hay need to RTD :)
Matthew Ferguson (Jun 19 2019 at 03:18):
Are there official namespaces for registration body identifiers? NZMC, NZNC etc
Daniel Thomson (Jun 19 2019 at 04:01):
@Matthew Ferguson I don't think there are URIs defined - something we need to do still
David Hay (Jun 19 2019 at 18:19):
Yes. We'd use NamingSystem resources to record these in fhir , but we need a good pattern for naming them @Peter Jordan @Alastair Kenworthy - any thoughts? How about:
https://standards.digital.health.nz/id/nzmz
https://standards.digital.health.nz/id/nznc
To be consistent with the ones for nhi / hpi etc?
Lloyd McKenzie (Jun 19 2019 at 21:39):
You might consider URLs that are actually canonical NamingSystem references. E.g. https://standards.digital.health.nz/fhir/NamingSystem/nzmz - that way if you host a FHIR server at https://standards.digital.health.nz/fhir, your canonical URL will resolve (and better yet, will resolve in a way that supports multiple content types)
David Hay (Jun 20 2019 at 00:02):
Interesting. Would you recommend considering the ones that have already been done:
NHI Number: https://standards.digital.health.nz/id/nhi
HPI Person Identifier: https://standards.digital.health.nz/id/hpi-person
HPI Organisation Identifier: https://standards.digital.health.nz/id/hpi-organisation
HPI Facility Identifier: https://standards.digital.health.nz/id/hpi-facility
I don't think that they've yet been used in production instances...
Lloyd McKenzie (Jun 20 2019 at 00:46):
It's worth considering at least
Peter Jordan (Jun 20 2019 at 01:02):
A design consideration/requirement was that these Identifier URLs may be used outside of FHIR. The current URLs for the NHI and HPI resolve to a Web Page - I'd prefer that, rather than them being canonical references to a Naming System resource.
Lloyd McKenzie (Jun 20 2019 at 02:56):
Ideally, the NamingSystem URLs should provide a web page if you don't specify an Accept header and provide the relevant JSON, XML, etc. if you ask for that. One of the reasons for choosing a NamingSystem rather than pointing to a URL maintained by a non-FHIR-aware agency is that they may well revamp their website and what used to resolve won't anymore. On the other hand, your NamingSystem entry maintained by a FHIR server is much less likely to get moved (because the people who manage it would yell and scream and jump up and down if someone tried) and the metadata on the NamingSystem entry can be updated from time to time to point to the authoritative website that describes the identifier.
Lloyd McKenzie (Jun 20 2019 at 02:57):
Note that I'm not saying that using the authoritative URL as the 'system' URL is wrong, just that it may have drawbacks.
Peter Jordan (Jun 20 2019 at 04:04):
One of the reasons for choosing a NamingSystem rather than pointing to a URL maintained by a non-FHIR-aware agency is that they may well revamp their website and what used to resolve won't anymore.
Well, in this case the URLs are maintained by the NZ Ministry of Health who are a FHIR-aware Agency and, in fact, sponsors of the project to create a FHIR API for the NZ Health Provider Index.
Igor Sirkovich (Jun 21 2019 at 03:30):
We are using NamingSystem for the URIs in Canada. Our base URL is https://fhir.infoway-inforoute.ca/NamingSystem, e.g. https://fhir.infoway-inforoute.ca/NamingSystem/ca-on-license-physician or https://fhir.infoway-inforoute.ca/NamingSystem/ca-ab-patient-healthcare-id. Having the URIs under the NamingSystem resource also helps us maintain mapping of the URIs to OIDs.
Last updated: Apr 12 2022 at 19:14 UTC
