FHIR Chat · Forge 16.5 for STU3

Stream: conformance

Topic: Forge 16.5 for STU3

Michel Rutten (Aug 18 2017 at 15:13):

Forge 16.5 for STU3 is now available for download from https://simplifier.net/forge.

This new release fixes some issues reported by the community and also introduces a couple of usability improvements. All users are encouraged to update to the current version.

FHIR API Improvements:

Update the FHIR .NET API library to 0.93.5-beta6
Stability improvements for DirectorySource
Handle bug in SimpleQuantity core datatype definition

Features:

NEW! Automatically initialize default slicing discriminator for type slices
NEW! FHIR Path expression validation

Bug fixes:

EXPERIMENTAL! Improved matching of base element types
Serialize constraints on meta.security.* and meta.tag.* elements to differential in proper order
eld-16 sliceName validation
Explicitly remove old child constraints after updating element type
Import resources from FHIR server and/or Simplifier
Fix broken hyperlink to Furore news page on Simplifier

Detailed release notes: https://simplifier.net/ui/OrganizationNews/Show?id=34

If you discover any issues or want to submit a feature request, please contact us.

Happy profiling!

Michel Rutten

Peter Jordan (Aug 22 2017 at 23:16):

Error Message when attempting to save a new Patient Profile in Forge 16.5..."Value cannot be null. Parameter name: resource Type". @Rob Hausam was also having this issue when trying to create a Profile on Observation at today's TermInfo Call. Any ideas, please? The XML view shows a populated value in the StructureDefinition-->type element.

Michel Rutten (Aug 23 2017 at 08:21):

Hi @Peter Jordan, can you please try to save to a clean (empty) output folder, see if that helps?

Peter Jordan (Aug 23 2017 at 08:33):

Thanks @Michel Rutten, that worked.

Michel Rutten (Aug 23 2017 at 09:27):

@Peter Jordan ok that's good to know. Still, I'd really like to solve these issues, as it is confusing to the end users.
Could you maybe share the contents of the originally selected output folder that triggered the error? Specifically files with .xml/.json extensions. Apparently the API stumbles on one of these files. Analyzing these files will allow us to improve the API to handle this gracefully.

Rob Hausam (Aug 23 2017 at 12:36):

Thanks, Michel. I'll give that a try, too. And I'll try to let you know what may be the offending files.

Michel Rutten (Aug 23 2017 at 13:25):

Hi @Rob Hausam, that would be very helpful! We've been trying to improve the API to gracefully handle invalid files and/or unknown file types. But I'm unable to reproduce this specific exception. If you could share (some of) the offending files, that would allow us to reproduce the error and improve the underlying logic. Thanks!

Peter Jordan (Aug 23 2017 at 21:01):

@Michel Rutten unfortunately, because I was attempting to install v16.5 and create a quick profile during a VC, I tried to save the profile in the root Documents Folder - not a smart move! There aren't any other XML/JSON files in that folder, but large number in the sub-folders (which include all my VS Dev Projects) - does Forge scan the underlying folders as well?

Michel Rutten (Aug 24 2017 at 07:29):

Hi @Peter Jordan, I see, that makes it hard to determine the offending file. I've looked at the logic, but I haven't found the culprit yet. Need to reproduce this.

Rob Hausam (Aug 24 2017 at 14:36):

@Michel Rutten, I'll see if I can find something that will help you sort this out.

Mirjam Baltus (Aug 24 2017 at 15:03):

@Rob Hausam I have been able to reproduce and have sent Michel the files. For me, it was some project.assets.json file in a subdirectory.

Mirjam Baltus (Aug 24 2017 at 15:04):

If you have any additional data that also can reproduce this, that can only help find the bug quicker, of course!

Rob Hausam (Aug 24 2017 at 15:04):

oh, great - I'll still look for what it is on my end and will send that along

Michel Rutten (Aug 25 2017 at 13:00):

Thanks to Mirjam's oustanding detective work, I've been able to locate and fix the offending logic. Apparently the issue was triggered by unrecognized/invalid JSON files on the target folder (or subfolders). The next release will silently ignore such files.

Rob Hausam (Aug 25 2017 at 16:38):

It appears that the fix is in 16.5.1? I didn't see it in the release notes, but I just tried it and saving in the same folder that I tried before seems to be working now. Thanks, Michel!

Brian Postlethwaite (Aug 27 2017 at 08:58):

Any chance of a DSTU2 release with just the resolver fix in it?

Michel Rutten (Aug 28 2017 at 08:52):

Hi @Brian Postlethwaite, sure, will do. Ewout tries to keep STU3 and DSTU2 branches in sync, by frequently backporting API improvements.

Brian Postlethwaite (Aug 28 2017 at 10:23):

I can update the DSTU2 branch with the changes, will co-ordinate with @Ewout Kramer

Ewout Kramer (Aug 31 2017 at 11:58):