Stream: implementers
Topic: NHS FHIR Publisher
Richard Kavanagh (Jan 08 2017 at 20:25):
We'll be pushing our publisher code out on to GitHub very shortly so if anyone's interested in knowing more about how it works then feel free to get in touch. Our code is developed using C# on .NET. Will make sure it is on GitHub before the WGM.
Grahame Grieve (Jan 08 2017 at 20:39):
it would be good if it produced, as part of the publication, an igpack.zip - that's what derivative tools will expect it from it - e.g. the validator, other ig publishers
Richard Kavanagh (Jan 08 2017 at 20:48):
It more or less does that now, though it was never a primary requirement of the tool. It may be the case in the future but for now not seeing an immediate need for the "ig" resource,
Grahame Grieve (Jan 08 2017 at 20:52):
actually, it's called validator.pack. It's a .zip file that contains:
- all the conformance resources (in json or xml)
- a version.info file that specifies the FHIR version details
- a json file that identifies the correct urls for external references to resources in the specification files
Grahame Grieve (Jan 08 2017 at 20:52):
this will allow people to use other FHIR tooling against the implementation guides you publish
Grahame Grieve (Jan 08 2017 at 20:53):
some of that is not formally documented, but it's pretty simple and we can document it
Richard Kavanagh (Jan 08 2017 at 20:54):
Well I guess that's the opportunity of open source, others can help us to this :-)
Grahame Grieve (Jan 08 2017 at 20:55):
sure. still, you could also get to this yourself - it would make it easy to use the standard FHIR validator against the IG, for instance
Grahame Grieve (Jan 08 2017 at 20:56):
(just reference the IG by it's publication URL, and the validator will pick the validator.pack, validate against it correctly, and put correct links for all the validation resource in error messages etc)
Richard Kavanagh (Jan 08 2017 at 20:59):
Worth looking at - its on the to do list...
Grahame Grieve (Jan 08 2017 at 20:59):
thx
Richard Kavanagh (Jan 15 2017 at 17:58):
Just pushed the current version of the tool to GitHub - https://github.com/InteropAdmin/FHIRGEN-DSTU2
Kevin Mayfield (Mar 08 2017 at 08:47):
@Richard Kavanagh does this support derived profiles? I'm looking at using CareConnect for the base profile and then adding our own extensions. So our FHIR resources will conform to CareConnect/NHS profiles but also include regional/trust extensions.
Richard Kavanagh (Mar 08 2017 at 09:05):
Kevin, I'm not sure we've never tried to do that. As far as we are aware Forge is still not quite in a place to do derived profiles reliably so we are not doing that at the moment. As an aside the CareConnect profiles were never really designed to be expanded in that way.
Michel Rutten (Mar 08 2017 at 10:12):
Hi @Kevin Mayfield Forge, the FHIR profile editor, supports authoring derived profiles for a while now. Some specific scenario's (e.g. involving slicing) still need a bit of effort. We're currently working on improving that. Don't hesitate to contact us if you find any issues.
Kevin Mayfield (Mar 08 2017 at 10:27):
Thanks. It's for internal training/research at the moment and in the last session we had a few comments about how we would do 'Z' segments. Was also looking how we would localise the profiles (for developers) e.g. for Patient.identifiers in the 'other' slice we would have specific guidelines on what the system should be :
Kevin Mayfield (Mar 08 2017 at 10:28):
Michel Rutten (Mar 08 2017 at 11:06):
@Kevin Mayfield You could create a derived profile and re-slice the "other" slice, to specify additional constraints on the system element. The Forge UI is not yet ready to let you create reslices. But if you manually edit the profile XML and add reslices (e.g. with slice names of the form "other/XXX"), then you should be able to open and edit the profile in Forge. We're planning to implement full support for re-slicing in Forge ASAP, but currently our main priority is to get STU3 release ready for the may WGM in Madrid.
Kevin Mayfield (Mar 08 2017 at 11:21):
That sounds ideal.
Kevin Mayfield (Mar 10 2017 at 15:38):
I've had a quick attempt at creating a derived profile with forge and it throws up a number of errors around missing extensions. Do I need to load in the extensions into the sessions beforehand? Forge147.png
Last updated: Apr 12 2022 at 19:14 UTC
