Stream: conformance
Topic: Forge 14.4 (NEW!)
Michel Rutten (Nov 25 2016 at 17:37):
A new Forge release is available: Forge version 14.4 for DSTU2 – FHIR DevDays 2016 Edition.
You can download the new release for free from http://www.simplifier.net.
The new Forge release includes some relatively large changes to critical functionality. You can read about the changes and new features here:
https://simplifier.net/ui/OrganizationNews/Show?id=22
The application includes a ReadMe.txt (displayed by the installer) that describes the recent changes in more detail – please read this carefully.
Highlight: this release introduces support for creating and editing profiles on profiles A.K.A. derived profiles! Not all advanced scenario's are supported yet (e.g. reslicing), this will be covered by future releases.
The new Forge version is published as an auto-update. Existing users of the official Forge install package will automatically be notified. For SLA customers, we also provide stand-alone binaries (w/o installer) and access to older releases.
The new release has a large number of high-impact changes, so it is not entirely unlikely that you will discover some regressions or new issues. In that case, please submit a bug report immediately. Be assured that we are committed to providing a stable application and will do our best to fix any submitted bugs as soon as possible.
If you have any questions, suggestions or bug reports, then we encourage you to contact us at forge@furore.com.
Happy profiling!
Michel Rutten (Nov 28 2016 at 13:22):
[Update] Due to some configuration changes, the new 14.4 release has received a new so-called application identity. This implies that Forge 14.4 is a new stand-alone application release. The previous Forge 13.2 release will not auto-update to 14.4. Instead, users must to download and install the 14.4 release manually.
After installing the 14.4 release, you will again receive notifications whenever an update has been published.
Jonny Rylands (Nov 28 2016 at 17:46):
@Michel Rutten Just to let you know the news link is not working (whether logged in to Simplifier or not)
Michel Rutten (Nov 28 2016 at 17:57):
Hi @Jonny Rylands thank you for the feedback!
After investigating, it appears that anonymous users have access to the Furore news feed on Simplifier:
https://simplifier.net/ui/Organization/Show/Furore
But not to individual items - "Access Denied" - woops! I'll notify our team to fix the access permissions.
Michel Rutten (Nov 28 2016 at 17:59):
Anyway the Forge download button on the homepage should still work...
Jonny Rylands (Nov 28 2016 at 17:59):
Thanks
Michel Rutten (Nov 28 2016 at 18:04):
Thank you for notifying us!
Jens Villadsen (Nov 29 2016 at 09:17):
@Michel Rutten There seems to be a bug when pressing "File->New Logical Model"
Binu DGIT (Nov 29 2016 at 09:21):
Can new forge publish profiles to HAPI2 server? I am trying to deploy the profile getting the following error
pasted image
Grahame Grieve (Nov 29 2016 at 09:22):
that isn't a valid value for the enumeration. where does it come from in the profile?
Binu DGIT (Nov 29 2016 at 09:24):
I was trying to publish the MyPatient as profile made out of Patient resource type using forge..
Grahame Grieve (Nov 29 2016 at 09:26):
if you look in the actual profile, where does 'SupportingDocumentation' appear?
Binu DGIT (Nov 29 2016 at 09:33):
This error displays while I try to connect the HAPI server and not found any "SupportingDocumentation" reference
Binu DGIT (Nov 29 2016 at 09:36):
Can I publish the custom profile as a StructuralDefinition resource type? I tried with HAPI server and failed.. Following error occurred
Error: HTTP 400 Bad Request: Resource ValueSet/administrative-gender not found, specified in path: StructureDefinition.snapshot.element.binding.valueSet[x]
Grahame Grieve (Nov 29 2016 at 09:44):
instead of publishing the profile to a server, save it to a file and look in it for SupportingDocumentation
Michel Rutten (Nov 29 2016 at 10:22):
@Jens Villadsen thank you for the bug report, I can reproduce the issue. Should have found that one myself, gues I was too focused on regular profiles...
Binu DGIT (Nov 29 2016 at 10:24):
I have done the same.. SupportingDocumentation does not exist..
Jens Villadsen (Nov 29 2016 at 10:26):
@Michel Rutten Thats the power of community-based development. You get to let others find your bugs ;)
Michel Rutten (Nov 29 2016 at 10:29):
@Jens Villadsen I managed to fix the bug in the development branch. Fix will be included in the next update. Thanks for reporting!
Michel Rutten (Nov 29 2016 at 10:30):
@Binu DGIT If you could send me the profile, then maybe I can investigate the cause of the error?
Binu DGIT (Nov 29 2016 at 10:36):
@Michel Rutten thank you very much for the response
Please find the attachment..
MyPatient.structuredefinition.xml
Michel Rutten (Nov 29 2016 at 10:42):
@Binu DGIT what is the address of the HAPI server instance that you are trying to publish to?
Binu DGIT (Nov 29 2016 at 10:43):
http://10.99.9.28:8055/fhir/baseDstu2
Michel Rutten (Nov 29 2016 at 10:45):
ok thx. BTW I notice the following documentation page on the public HAPI server:
https://fhirtest.uhn.ca/resource?serverId=hapi_dev&pretty=false&resource=SupportingDocumentation
Seems like HAPI supports a custom resource type. Forge probably stumbles when processing the conformance statement. But Forge should be able to gracefully handle custom resource types.
Michel Rutten (Nov 29 2016 at 10:49):
@Binu DGIT I can't seem to reach the server... is it public?
Binu DGIT (Nov 29 2016 at 10:50):
sorry, it is not public... in our environment.. I tried your link.. seems working properly .. so Issue might be in our server environment..?
Michel Rutten (Nov 29 2016 at 11:00):
@Binu DGIT In earlier versions of the FHIR .NET API (used by Forge), the deserializer was not able to handle unknown enumeration values (such as ResourceType). So older Forge versions failed to open any resources with unknown/unofficial codings etc. However we've changed the API and Forge to try and gracefully handle unknown enumeration values. Considering that the reported error message is complaining about an unknown ResourceType, we probably missed a spot. So if we can reproduce the issue, we should be able to pinpoint the offending line of code and fix it.
Michel Rutten (Nov 29 2016 at 11:03):
Unfortunately the public HAPI server requires client authentication via OAuth2, whereas Forge currently only connects to servers with basic authentication. So I can't investigate this issue against the public DSTU2 HAPI instance.
Binu DGIT (Nov 29 2016 at 12:11):
I tried with the public HAPI server and could upload MyPatient profile successfully. So issue might be with my local HAPI server environment..
Michel Rutten (Nov 29 2016 at 12:21):
@Binu DGIT Since Forge does not support OAuth, how did you publish the resource?
Michel Rutten (Nov 29 2016 at 14:40):
@Jonny Rylands we've fixed the access permissions on the news feed items in Forge & Simplifier. So you should now be able to open a news item from within Forge. Thank you for reporting the issue!
Patrick Werner (Dec 02 2016 at 09:32):
@Michel Rutten i've encounterd the following bugs:
- can't create new Extension or Logical Model
- can't open profiles created with the old Forge Version if they are saved as differential profiles, snapshots are working
- can't import this profile from simplifier: https://simplifier.net/PatricksEgkSandbox/persoenlicheVersicherungsdaten
Michel Rutten (Dec 05 2016 at 10:09):
Hello @Patrick Werner, thank you for the feedback! The initial 14.4 release indeed contains a couple of annoying bugs. We've already fixed a couple and will publish a hotfix release shortly. Stay tuned...
BTW I cannot find/access the linked profile on Simplifier. Maybe it is private? Alternatively, could you submit the profile via e-mail?
Last updated: Apr 12 2022 at 19:14 UTC
