FHIR Chat · Forge · implementers

Stream: implementers

Topic: Forge

Michel Rutten (Mar 10 2016 at 13:03):

A new Forge release (12.2) is now available for download.

This release introduces a new application versioning scheme.

• The major release version represents the sequence number of the next HL7 FHIR Connectathon.
• The minor release version represents the current sprint.
• An optional third version component indicates an intermediate hotfix release.

Highlights in this release:

• Support for complex extensions
  Now you can create and edit complex extensions with nested child elements
  Also Forge now supports extensions on extensions.

• Automatically rename choice type elements constrained to a single type
  e.g. value[x] constrained to Boolean => valueBoolean

• Optionally display common inherited resource elements derived from the abstract Resource and DomainResource base types:
  Resource.id
  Resource.meta
  Resource.implicitRules
  Resource.language
  DomainResource.text

• Improved support for the ImplementationGuide resource
  Reorder package entries
  Edit the ImplementationGuide.dependency component
  Edit the ImplementationGuide.contact component
  Edit the ImplementationGuide.page component

• Improved validation, especially for element type constraints

• Miscellaneous UI improvements
  Element cardinality hints
  Validation warning color expresses the severity
  Blue = Info, Orange = Warning, Red = Error
  When creating or opening a new resource, activate the Element Tree tab by default
  Generate unique names & urls for newly created resources using an autonumbering scheme
  Compact redesign for the file properties panel
  A command button next to the file location opens the containing folder in the Windows File Explorer.

• Improved performance, especially when opening new resources.

You can download the new relase from http://fhir.furore.com/forge

If you have any questions or comments, you can contact us at forge@furore.com.

Happy profiling!

David Hay (Apr 06 2016 at 23:53):

hi michel - when I try to directly upload a profile to a fhir server I get an 'object reference not set to instance' error....

David Hay (Apr 06 2016 at 23:54):

also - is there a simple way of updating forge, or is it best to always download a new version

David Hay (Apr 07 2016 at 03:39):

oh - and after getting the error, attempting a save will result in the save error...

Michel Rutten (Apr 07 2016 at 08:32):

@David Hay thank you for reporting this issue. We've recently received a similar bug report. It turned out that the connection error was caused by a mismatch on the resource wire format (JSON instead of XML). This will be fixed in the next release.
If you have downloaded the official ClickOnce package, than the installer automatically checks for updates at application launch. However if you are running stand-alone binaries, then you need to update manually.
I'll send you a link via e-mail to the latest internal development build, so you can test if the connection issue has been fixed.

Reuben Daniels (Apr 11 2016 at 01:10):

Is it possible to put constraints around contained resources and modifierExtensions when creating a profile in Forge?

Grahame Grieve (Apr 11 2016 at 04:25):

ask this in the conformance stream

Reuben Daniels (Apr 11 2016 at 04:25):

will do

David Hay (Apr 11 2016 at 23:40):

When creating a profile in forge, is it possible to remove elements with a multiplicity of 0..0 from the snapshot?

Lloyd McKenzie (Apr 12 2016 at 03:13):

Why would you want to?

David Hay (Apr 12 2016 at 03:20):

What is the value in their being present?

Lloyd McKenzie (Apr 12 2016 at 03:21):

It's explicit. When we get into versionless, it'll differentiate between known prohibited elements and unknown new elements.

David Hay (Apr 12 2016 at 03:22):

Different questions: Forge adds the following snippet when adding an extension:

  <element>
      <path value="CarePlan.extension" />
      <slicing>
        <discriminator value="url" />
        <rules value="openAtEnd" />
      </slicing>
    </element>

Which causes Grahames server to reject it on the basis of invariant SDF-3: On StructureDefinition.snapshot: Each element definition in a snapshot must have a formal definition and cardinalities

Lloyd McKenzie (Apr 12 2016 at 03:26):

Forge should probably be carrying the definition and cardinality of the base extension element

David Hay (Apr 12 2016 at 03:27):

and place it in that element?

Grahame Grieve (Apr 12 2016 at 03:27):

yes that's what a snapshot means

Michel Rutten (Apr 12 2016 at 08:13):

@David Hay thank you for pointing this out. I will fix the snapshot serialization of the slicing intro element.

Michel Rutten (Apr 12 2016 at 08:15):

Created Jira issue FRG-308

David Hay (Apr 12 2016 at 08:18):

thanks michel - btw - will you be continuing to support the STU-2 version of forge?

Michel Rutten (Apr 12 2016 at 08:28):

@David Hay correct, Forge will stay at DSTU2 until after the Montreal HL7 WGM. After STU3 balloting, we will upgrade all our tooling to STU3, including a new major Forge release for STU3. You can run different major Forge releases run side-by-side. Older Forge releases are no longer actively maintained, but will remain available for download. We do provide support on older versions to customers with a service level agreement.

Michel Rutten (Apr 26 2016 at 14:00):

Forge Release 12.4 for DSTU2 1.02 is now available for download.

Highlights:
- Upgrade FHIR .NET API library to v0.95-alpha1 for DSTU2 1.02 (Official version)
The new FHIR API version provides several bugfixes and optimizations.
- New online F1 help: http://docs.simplifier.net/projects/forge-docs/
- Display resource maturity level, as defined by the FHIR specification
- Support editing of the Narrative component (DomainResource.text)
Note: the Narrative component contains formatted text and can be quite large.
Forge provides two global configuration options in order to conserve memory:

• Discard DomainResource.text values
  Delete the Narrative component when loading a (core or user) profile

• Discard DomainResource.text profile element
  Delete ElementDefinitions for the Narrative component in all (core or user) profiles

• Optimized Differential generation
  The serialized XML output is now more compact and contains less noise.
  All omitted values are implied to be derived from the base resource.
• New configuration option "Show common elements"
  This option toggles the visibility of common profile elements derived from Resource & DomainResource
• Support for hyperlinks in error dialogs
• Various optimizations and bugfixes

If you have installed Forge from the ClickOnce installer package, then the application will automatically offer an upgrade to the new release on the next launch. Alternatively, you can download the new release from https://simplifier.net/ui/info/forge.

In case you find a bug in this new release, please report it to us ASAP at forge@furore.com and we will try and fix it before the upcoming HL7 Montreal WGM. Also, if you have any questions or comments, feel free to contact us at forge@furore.com.

Happy profiling!

Igor Sirkovich (Apr 26 2016 at 14:16):

Thank you Michel! I'm wondering if there is a plan to release a new version of Forge to support STU3 Candidate / 2016May version of FHIR.

Michel Rutten (Apr 26 2016 at 14:18):

@Igor Sirkovich You're welcome! We are definitely planning to upgrade all our tools (including Forge) to STU3, but not until _after_ the HL7 WGM ballot.

Igor Sirkovich (Apr 26 2016 at 14:19):

Thank you, will have to wait :)

Lloyd McKenzie (Apr 26 2016 at 15:52):

Michel, if someone were to produce a DSTU 2 version of the DSTU 3 resource StructureDefinitions, Forge would be able to work with those, right? The main updates for you in moving to DSTU 3 would be accommodating the changes in StructureDefinition and ValueSet, but my understanding is that you now take the resource definitions from a library, so it's easy to swap those out with a different set?

Grahame Grieve (Apr 26 2016 at 16:24):

ContentReference is a big change

Ewout Kramer (Apr 26 2016 at 18:18):

Yes, the breaking change in StructureDefinition is what keeping us from simply upgrading to STU3...

Lloyd McKenzie (Apr 26 2016 at 19:58):

But if the DSTU3 structured definitions were converted to DSTU2 syntax, could Forge handle that?

Michel Rutten (Apr 26 2016 at 21:25):

@Lloyd McKenzie Unfortunately it's not that easy. Forge depends on StructureDefinition POCO in FHIR .NET API. In STU3, StructureDefinition resource introduces breaking changes, so this requires a new major release. We want to make sure that DSTU2 users are still able to edit their existing resources. Therefore the STU3 upgrade will be published as a new major version that you can install next to the current DSTU2 release. We will upgrade all our tooling to DSTU3 after the Montreal WGM ballots. In theory, it's possible to hack validation.zip for STU3 support, enabling the profiling of STU3 clinical resources using the DSTU2 StructureDefinition. But I wouldn't recommend that to regular users...

Michel Rutten (Apr 26 2016 at 21:37):

@Lloyd McKenzie if there is a pressing need, we might be able to hack a STU3 validation.zip. But I'm a bit reluctant, worried that profiles for STU3 resources expressed by DSTU2 StructureDefinitions will cause confusion to the community...? However if you think this would be valuable nonetheless, then I'm willing to cooperate and try to get this working for Montreal. Note that Forge uses the validation.xml.zip from the application directory. If you replace the StructureDefinitions in this ZIP file (esp. inside profile-resources.xml) then Forge should pick this up on the next run.

Michel Rutten (Apr 26 2016 at 21:40):

BTW Tomorrow I'm celebrating King's Day so I'll be offline. Leve de koning! Hoera! Hoera! Hoera!

Lloyd McKenzie (Apr 27 2016 at 00:28):

@Michel Rutten I don't think it should be terribly confusing to the community to have a "2016May validation.zip" or a "2016 ballot validation.zip" file for use with Forge. If you really think there might be confusion, throw a _readme.txt file in the zip that explains that the resources are documented using DSTU 2 artifacts because that's what Forge currently supports. If we're going to push HL7 to start using Forge for development, it's going to be a pretty standard process to need to edit profiles based on the "next" release of FHIR using tools built against the "current" release of FHIR.

David Hay (Apr 27 2016 at 01:36):

can you give an example of the use of contentreference?

Ewout Kramer (Apr 27 2016 at 13:15):

Yes, I think if we'd had the new STU3 resources in DSTU2 SD format, we could proceed, but since there are also changes with regards to NamingSystem/ValueSet, I suspect there are some subtle issues that would make this harder than it sounds....

Grahame Grieve (Apr 27 2016 at 13:16):

you know I have a converter that will convert from DSTU 2 to STU 3 format and vice versa?

Ewout Kramer (Apr 27 2016 at 13:16):

VIce versa? I know about 2->3, but not vice versa no.

Grahame Grieve (Apr 27 2016 at 13:17):

yep. my converter will go both ways

Ewout Kramer (Apr 27 2016 at 13:17):

If you made it work, I guess "all" we'd need was the stu3 definitions in DSTU2 SD format....

Michel Rutten (Apr 29 2016 at 09:05):

Is there a validation.zip (or actually just profiles-resources.xml / profiles-types.xml) available that contains updated STU3 resource definitions expressed in DSTU2 StructureDefinitions? I could try and examine if I can make Forge use the updated definitions. Unfortunately I have little time left to implement user friendly integration and iron out any bugs, so I'm not sure we can get this to work in time for Montreal.

Michel Rutten (May 07 2016 at 18:20):

Forge Release 12.5 for DSTU2 1.02 is now available for download.

Forge is a Windows application for FHIR Profiling & Conformance based on the Microsoft .NET platform. The application is freely available for download and free to use.

Note: this release still supports FHIR DSTU2 1.02 (Official version) from Oct. 24th, 2015.
After the HL7 WGM ballots in Montreal, we will upgrade all our FHIR tooling to support the new STU3 specification. Because STU3 introduces breaking changes, we will publish the future Forge STU3 release as a new major version. This will allow side-by-side deployment of both the DSTU2 and STU3 releases on the same machine.

Highlights:

• NEW! Logical modelling
  Forge now supports the authoring of logical models, based on the FHIR StructureDefinition resource.

• New start page
  The application start page now displays a news feed from https://simplifier.net/feed/organizationnews/furore
  The news feed will inform you about product updates, new major releases and upcoming events such as HL7 WGM.
  The new start page also provides shortcuts to frequently used commands and recent documents.

• Various optimizations & bugfixes

You can download Forge from our Simplifier website: https://simplifier.net/ui/info/forge

Happy Profiling!

Richard Kavanagh (May 09 2016 at 23:10):

The link https://simplifier.net/ui/info/forge appears to be broken at the moment

Martijn Harthoorn (May 10 2016 at 07:37):

Thanks. We're fixing it.

Martijn Harthoorn (May 10 2016 at 08:12):

Richard: We fixed it. It should be working again.

Michel Rutten (Jun 10 2016 at 15:01):

A new Forge version (13.2) is now available for download from https://simplifier.net/.
This update represents a minor release with lots of bugfixes and small functional improvements.

New commands:

- New command in File menu: Open in External Application
(also available in session explorer context menu)
Open the selected resource via windows, using the default application registered for the (.xml) filetype
This allows you to edit package entries that are not (fully) supported by Forge itself, e.g. ValueSets, example resources etc.

- New command in Options menu: Open application folder
The ClickOnce installer puts the application files in a deeply nested folder that is hard to find.
This command opens the application installation folder in Windows Explorer.

- New command: show official documentation for the selected element
The profile elements tree now provides a new toolbar command (with question mark "?" icon)
to visit the official online FHIR documentation page for the selected profile element.

Optimizations:

- Optimized differential component for size
Serialization logic has been further improved in order to suppress the serialization
of nodes with empty/default Integer or Boolean values (e.g. Min, MustSupport).

- Optimized profile (re-)binding
Forge tries to bind element types to the associated profiles, if they are available (loaded) within the current context, for validation purposes.
Type binding requires Forge to match compatible profiles, this is quite computationally intensive.
The underlying logic has been optimized to prevent unnecessary rebinding.
Specifically, Forge now ignores changes in element type options that aren't selected/checked.
This optimization improves the performance of change tracking, e.g. when loading a package
or editing the canonical url of a profile that is referenced by other loaded profiles.

Plus a plethora of bugfixes...

If you have any questions or comments, please contact us at forge@furore.com.

Happy Profiling!

Shweta Katdare (Jun 16 2016 at 15:17):

I am trying to create a Profile for Bundle using Forge. Cardinality on entry is set to 0-*. I want to set constraint on the type of resource in an entry like a bundle should have atleast one Allergy Intolerance resource, a patient resource etc. How can I edit the entry in Element Tree ?

Michel Rutten (Jun 16 2016 at 15:38):

Hi @Shweta Katdare sounds like you need to slice the Bundle.entry element. Slicing allows you to define multiple constraints on a single element. Forge provides a toolbar button to slice an element, and another button to add so called "slices". You can add a slice for each separate resource type, e.g. first slice has type set to Reference(AllergyIntolerance) and cardinality set to 1...1.

Michel Rutten (Jun 16 2016 at 15:40):

e.g. see this Bundle profile on simplifier: https://simplifier.net/RippleOSIUK/Bundle-ProvideDocumentBundle

Michel Rutten (Jun 16 2016 at 15:41):

Here you can find an explanation of slicing: https://www.hl7.org/fhir/profiling.html#slicing

Shweta Katdare (Jun 16 2016 at 16:42):

Got it ! Thanks @Michel Rutten

Shweta Katdare (Jul 07 2016 at 12:50):

Hi all, a quick question. I create a profile in Forge with very minimum changes, say changing cardinality of an element. I can publish that profile to http://spark-dstu2.furore.com/ without any issues. When I try to publish it to http://fhir2.healthintersections.com.au/open, I encounter following error 'Constraints must be unique by key () constraint.distinct(key)'. So the question is why do the 2 servers behave differently ? Do i really need to add 'Constraints' when it has differential statements ?

Michel Rutten (Jul 07 2016 at 12:53):

Hi @Shweta Katdare No you don't need to explicitly add constraints to a profile. I suspect that this is a bug in @Grahame Grieve's server.
What base resource did you choose?

Shweta Katdare (Jul 07 2016 at 13:00):

I am using MedicationOrder as base resource.

Michel Rutten (Jul 07 2016 at 13:06):

Hi @Shweta Katdare, I checked the (DSTU2) core resource definition of the MedicationOrder resource. I found out that the MedicationOrder.text element has a condition reference "dom-1". This refers to a constraint that is defined on the DomainResource base type profile. Possibly Grahame's server does not yet have the capability to resolve the inherited constraint.

Shweta Katdare (Jul 07 2016 at 13:10):

Thanks for checking @Michel Rutten

Michel Rutten (Jul 07 2016 at 13:10):

You're welcome!

Shweta Katdare (Jul 07 2016 at 14:26):

so can you point me to a public server where I can publish the profile and validate it ? I tried http://spark-dstu2.furore.com/ but Validate operation is not implemented on it

Ioana Singureanu (Jul 07 2016 at 15:08):

Is Forge going to support the latest ballot STU3 resource definitions? I would like to create a profile for a newly created resource.

Shweta Katdare (Jul 07 2016 at 20:29):

I created an extension in Forge with 3 extensions nested in it, and published it to a public test server. I've a screenshot attached. Is this correct way to create complex extensions ? i do need 3 distinct boolean values.
extensions.png

Grahame Grieve (Jul 07 2016 at 20:45):

@Michel Rutten, this is my server applying standard FHIR validation is specified in the spec, where as Spark doesn't. This is unlikely to be a bug in my server, more likely a bug in Forge. But I haven't had a chance to look at the actual profile yet

Grahame Grieve (Jul 07 2016 at 21:06):

@Ioana Singureanu the current ballot publishes a set of DSTU2 profiles that you can configure Forge to use - that way you can use Forge against newly created resources.

Grahame Grieve (Jul 07 2016 at 21:06):

and the new IG publisher is able to use DSTU 2 profiles created in that way

Ioana Singureanu (Jul 08 2016 at 00:24):

@Grahame Grieve I have already created DSTU2 profiles but they are based on Contract and I would to do the same for Consent. The good news is that I will only require a profile for Consent without the List and Basic profiles needed with Contract. If Forge allows me to use STU3 FHIR Consent. that would be great.

Grahame Grieve (Jul 08 2016 at 00:26):

yes. the downloads page from the current build has a link to the forge version of the resources. @Lloyd McKenzie can tell you how to hack Forge to use those definitions instead. In a future release, that's supposed to become easier

Lloyd McKenzie (Jul 08 2016 at 01:39):

You can't hack Forge to use new resources, only new definitions of old resources. Yet. The ability to handle "new" resources is supposed to be coming soon.

Shweta Katdare (Jul 08 2016 at 18:17):

can we validate extensions using $validate operation ?

Shweta Katdare (Jul 08 2016 at 20:12):

Everytime I add an extension to a resource (in Forge), I get this warning. How do I edit it ?
pasted image

Grahame Grieve (Jul 08 2016 at 21:12):

yes validate includes validating exntensions

Vadim Peretokin (Jul 11 2016 at 04:15):

what's the recommended version of forge to be used with fhir 1.4.0?

Grahame Grieve (Jul 11 2016 at 04:25):

there isn't really one

Grahame Grieve (Jul 11 2016 at 04:26):

Forge itself only supports 1.0.2. The trunk - 1.5.0 - supports Forge by converting to and from 1.0.2, but this isn't a solution for 1.4.0

Vadim Peretokin (Jul 11 2016 at 04:27):

alright

Michel Rutten (Jul 11 2016 at 09:35):

@Shweta Katdare Maybe you can share your MedicationOrder profile? I'd like to take a closer peek in order to explain the validation error about constraint keys.

Michel Rutten (Jul 11 2016 at 09:42):

@Shweta Katdare concerning the validation error on the element Base definition property, this shouldn't happen as the user cannot edit these fields. Are you using the current Forge release? I've checked but cannot reproduce this in the current (unpublished) development branch. Does the warning occur on the added extension element? Or can you outline steps to reproduce?

Shweta Katdare (Jul 11 2016 at 12:17):

@Michel Rutten I've attached the MedicationOrder profile. The only change is cardinality of medicationCodeableConcept and it's type.

Shweta Katdare (Jul 11 2016 at 12:20):

mymedorderstructuredefinition.xml

Shweta Katdare (Jul 11 2016 at 12:23):

@Michel Rutten I am using Forge 13.2. The warning occurs when I add the extension on a resource. I've attached both the profiles testextensionstructuredefinition.xml basicwithtestextensionstructuredefinition.xml

Michel Rutten (Jul 11 2016 at 16:17):

@Shweta Katdare thank's for the info. I've taken a quick look at your MedicationOrder profile. I noticed that the profile contains an expanded snapshot component. This seems to cause the validation errors on Grahame's server. Snapshot expansion in Forge is somewhat crude and not fully compliant to the FHIR spec. I'm planning to remove this custom logic and instead leverage the snapshot expansion logic that is now provided by the FHIR .NET API. This should improve the quality of the snapshot expansion and better conform to the FHIR spec. This improvement will probably be part of the next release. For now, you can try and save your profile without a snapshot (by unchecking the relevant setting in the Forge options menu) and then republish to Grahame's server. This should fix the validation error, as the server will then expand/resolve the snapshot component itself. If not, please let me know.

Michel Rutten (Jul 11 2016 at 16:36):

@Shweta Katdare as for the validation warning on the extension element, I cannot reproduce this in the current internal development branch, so I assume that I've already fixed this lately. The bugfix will be part of the next Forge release (no pub date yet).

Shweta Katdare (Jul 12 2016 at 14:44):

thank you @Michel Rutten . I tried publishing the profile without snapshot component. It gives me 'constraints must be unique by key...' validation on the root element.

Michel Rutten (Jul 12 2016 at 14:59):

@Shweta Katdare strange, I'd have to investigate further. @Grahame Grieve maybe you can explain the reason of the validation error? The MedicationOrder profile should be on your server. If I understand what's wrong, I can try and fix it.

Shweta Katdare (Jul 12 2016 at 15:23):

@Michel Rutten Here is the profile without snapshot mymedorderstructuredefinition.xml. Thanks for your help

Grahame Grieve (Jul 12 2016 at 19:31):

hmm, this it turns out, is a bug in my server

Shweta Katdare (Jul 13 2016 at 13:08):

@Michel Rutten I was able to get rid of the warnings by explicitly adding <base> element in the generated structured definition and re-opening it in Forge. Thanks for your help.

Michel Rutten (Jul 13 2016 at 13:16):

@Shweta Katdare Did you create the original profile (without base element) in Forge? Because Forge should always initialize and emit the ElementDefinition.base component. If not, then you probably found a bug. Anyway, thank you for reporting this! When you open an external profile in Forge, the application already tries to find and fix some common issues. Maybe we should improve that logic to also detect and fix missing ElementDefinition.base components.

Shweta Katdare (Jul 13 2016 at 13:34):

I do have the 'Save ElementDefinition.Base' option turned on.

Michel Rutten (Jul 13 2016 at 14:37):

@Shweta Katdare I can't reproduce the warning in the current (internal) development branch, so I guess I already fixed it. When you add an extension element, the ElementDefinition.base component is initially empty. However this does not trigger any validation warnings. In any case, I think you can safely ignore the warning and assume that this will no longer occur in the next update (no publish date yet).

Jayashree Surnar (Apr 18 2017 at 06:05):

hello all, some where i read that , forge tool for stu3 support will release 17th april. but i didn't find it anywhere. so please can any one help. from where i can download that. Thank you.

Vadim Peretokin (Apr 18 2017 at 07:07):

Would you have a link for that date?

Michel Rutten (Apr 18 2017 at 08:56):

Hi @Jayashree Surnar Although we did not commit to a specific date, we are planning to publish a sneak preview Forge STU3 release shortly, probably later this week. Once the release is available, we will publish an announcement on Zulip and to the Simplifier/Forge news feed. Stay tuned!

Jayashree Surnar (Apr 18 2017 at 10:02):

okay. Thank you @Michel Rutten

Brett Esler (Apr 18 2017 at 22:05):

+1 thanks @Michel Rutten

Brian Reinhold (Apr 19 2017 at 08:35):

Any news on the release of Forge? I can't work on my profile because of a bug in the 15.4.0 version of Forge that prevents loading the saved profile. For my case the STU3 support is not nearly as critical as just being able to continue working! Perhaps the bug can be fixed for the DSTU2 version?

Michel Rutten (Apr 19 2017 at 10:08):

Hi @Brian Reinhold we will publish a sneak preview release of Forge for STU3 to the community this week. We will continue to provide support and updates for Forge for DSTU2 to our commercial customers.

John Moehrke (Apr 19 2017 at 11:32):

@Elliot Silver do we have a slot on the IHE face-to-face next week where @Michel Rutten can present Forge as a tool for profiling FHIR?

Elliot Silver (Apr 19 2017 at 16:40):

Not yet. Let me see if I can make room for it. We might have to organize a separate session for this.

Emma Jones (Apr 19 2017 at 18:58):

Can PCC join when you schedule it please?

Elliot Silver (Apr 19 2017 at 19:08):

Hi @Emma Jones, certainly, I'll let you know when I've got more.

Emma Jones (Apr 19 2017 at 19:27):

Thanks Elliot

David Hay (Apr 20 2017 at 17:58):

Actually, I think a number of folk would be interested in a session on Forge!

Brian Reinhold (May 04 2017 at 18:38):

Any news on this? I attempted a download from Simplifier and got a 'cannot process request' response

Michel Rutten (May 05 2017 at 16:31):

@Brian Reinhold we've just updated our Simplifier platform to support STU3. The public endpoints have also been updated to STU3. Although Simplifier remains to support DSTU2 resources, Simplifier does no longer provide public DSTU2 endpoints. If you want to use Forge/Simplifier integration features (open from, publish to), then you must upgrade to Forge STU3.

Martijn Harthoorn (May 08 2017 at 23:41):

@Brian Reinhold - do you still have this issue? If so, can you give me some details?

Jayashree Surnar (May 09 2017 at 06:35):

hello all, whenever i trying to save my profile as snapshort then it's getting struck. don't know why? if i'm saving as differencial then it's working fine. any reason?

Lloyd McKenzie (May 09 2017 at 07:51):

Forge questions should ideally be raised on the conformance stream

Michel Rutten (May 09 2017 at 10:18):

Thank you for the bug reports. I'm now attending the HL7 WGM and then I'll have a couple of days off. I'll look into this next week or the week thereafter. Then we'll try to fix all the reported bugs and publish a minor update. Cheers!

Jayashree Surnar (May 10 2017 at 03:57):

okay.

Jens Villadsen (May 22 2017 at 08:14):

"This MAY not be not the Service Delivery Location's Organization." @Michel Rutten - in forge in Encounter.serviceProvider

Jayashree Surnar (Jun 05 2017 at 09:53):

hello @Michel Rutten , i want to create ccda on fhir(stu3)for history and physical using forge. how to add multiple sections to composition profile any suggesions plz.(for example in Observation for BP we have 2 componets. i don't undesrtand how to add to the profile) Thank you.

Michel Rutten (Jun 05 2017 at 14:25):

Hi @Jayashree Surnar, FHIR profiles support a technique called slicing (also supported by Forge). Slicing allows you to define multiple constraints for the Composition.section array element. This is quite typical for ccda composition profiles, so you can probably find some existing (example) profiles online. Otherwise @Rick Geimer may be able to help you out.

Jayashree Surnar (Jun 06 2017 at 04:22):

okay. Tnq @Michel Rutten

Mounika (Dec 12 2017 at 11:20):

Hi @Michel Rutten I have created a profile using Forge. But when I am saving that profile it's getting stuck and not working. How can I fix it?
Thank you.

Michel Rutten (Dec 12 2017 at 11:24):

Hi @Mounika, can you provide more detailed information? What do you mean with "stuck", does the application hang while saving? Try to disable "save snapshot" in the options menu, see if that works.
Note: to generate the snapshot, Forge tries to resolve all external (profile) references from the containing directory. Forge will report issues from snapshot generation, such as unresolved references.

Mounika (Dec 12 2017 at 11:47):

@Michel Rutten I have already disabled that option still the application is not responding.

Michel Rutten (Dec 12 2017 at 11:49):

Can you share the profile?

Mounika (Dec 12 2017 at 12:09):

I got the problem fixed. Thank you.

Werner De Mulder (Dec 06 2020 at 21:06):

(deleted)

Grahame Grieve (Dec 06 2020 at 22:56):

what FHIR version are you working with?

Sree Ram (Dec 17 2020 at 19:45):

Hi All,
I am trying to understanding FHIR OrganizationAffiliation profile extensions to prepare a mapping document. I see that FHIR provided profile excel file downloads without extensions in the file. Where do i find the file with extensions?

• If there is no file with all the extensions , do i need to add extensions that FHIR provided (taking OrganizationAffiliation as example https://build.fhir.org/ig/HL7/davinci-pdex-plan-net/StructureDefinition-plannet-OrganizationAffiliation.html) add them manually or by usnig FORGE? or is there any other way to get the extensions with the profile?

Last updated: Apr 12 2022 at 19:14 UTC