Stream: clinFHIR
Topic: updates
David Hay (May 14 2016 at 21:24):
Hi Guys - thanks for coming to the Clinicians challenge yesterday and giving me all that great feedback on clinFHIR - I really appreciate it! I'll work through the issues as I have time - and will notify through this channel as they get uploaded. I did have some time travelling back to New Zealand so I was able to do a couple of things:
- You can view a patients existing resources as XML - and download them to the local machine also (This is to support using clinFHIR to generate samples - especially for Melva and John :) )
- When creating a resource instance and wanting to create a reference to an existing one, there's now a link (just under the dropdown) that will display the resources of that type in a dialog with a complete json representation of the resource than you can use to better select the resource
David Hay (May 14 2016 at 21:25):
I think this channel is probably the best way to send feedback - so keep it coming!
cheers...
Melva Peters (May 16 2016 at 16:06):
Much appreciated David! Any further thought on what needs to be done so that we can be referencing the most current build for the resource to enable us to create instance examples for the upcoming STU3 Release?
David Hay (May 16 2016 at 17:47):
@ Bob Milius The latest version now has the ability for you to enter 'ad-hoc' codes for a codeable concept. There's no validation performed (other than the usual server based stuff) so you can enter what you want! It would be feasible to add simple validation - eg using the 'ValueSet/$validate-code' to see if it is in some other ValueSet, or maybe CodeSystem/$lookup might be a better choice. thoughts?
David Hay (May 16 2016 at 17:49):
@Rob Hausam - it occurs to me that the CodeSystem/$lookup may meet your requirements as well...
Bob Milius (May 16 2016 at 19:32):
Thanks, David! I see it includes entries for system, code, and display. The only thing I'd add right now is the version element.
Rob Hausam (May 17 2016 at 01:07):
David, I think that CodeSystem/$lookup probably makes the most sense in this context - that should be useful
David Hay (May 17 2016 at 02:33):
@Rob Hausam funny you should say that...
If you take a look at the latest version, you now have the ability to do a lookup based on CodeSet/$lookup. Having found a code you can navigate up and down the hierarchy (assuming it has one - like SNOMED) from links supplied by the service. You can also first find the concept you want by searching within the binding (ValueSet/$expand), and then select the 'navigate' tab to traverse the hierarchy as well.
This stuff is just too easy...
David Hay (May 17 2016 at 02:34):
(though the UI does require a bit more love and attention...)
Last updated: Apr 12 2022 at 19:14 UTC
