Stream: social
Topic: ForgeForMac
Mritunjay Dubey (Aug 18 2016 at 06:18):
Hello team,
what is the recommended way to use forge for profile building on MacOS. have anyone tried it already ?
I have tried it using mono but doesn't work.
Michel Rutten (Aug 18 2016 at 08:40):
Hello @Mritunjay Dubey. Forge is a .NET WPF desktop application for Windows. So you can't run the application directly on MacOS. Also you can't run Forge on Mono, because Mono doesn't support WPF. As a workaround, you could install Windows within a virtual machine (e.g. Parallels Desktop) and run it from there.
Mritunjay Dubey (Aug 18 2016 at 08:42):
@Michel Rutten thanks for your reply, I will try that out.
Michel Rutten (Aug 18 2016 at 08:45):
@Mritunjay Dubey no problem. I've seen users do this, so it should work.
Michael Osborne (Aug 18 2016 at 10:07):
Maybe they should rewrite it in electron.
Mritunjay Dubey (Aug 19 2016 at 06:39):
is there a wiki for how to use this? E.g. I want to add a extension blood group how actually I should do it ?
Mritunjay Dubey (Aug 19 2016 at 06:40):
I have seen a wiki for http://clinfhir.com/ and that was simpler, but I want to try out forge
Michel Rutten (Aug 22 2016 at 09:03):
Hi @Mritunjay Dubey here you can find some basic documentation about Forge:
http://docs.simplifier.net/projects/forge-docs/en/latest/
Documentation is work in progress. A colleague of mine has been working on new and updated content, so stay tuned.
Michel Rutten (Aug 22 2016 at 09:09):
It's fairly easy to create and use an extension in Forge:
- Use command "New Extension" to create a new extension definition. Make sure to provide an absolute canonical url that uniquely identifies your extension, e.g. http://example.org/fhir/StructureDefinition/MyExtension
- Use command "New Profile" to create a new resource profile.
- Select a parent element that you want to extend and click on the "Extend" toolbar button. Forge will add an extension element as a child of the selected parent element.
- Select the extension element if necessary. In the Properties pane in the right column you can map the extension element to an existing extension definition. The drop-down box provides access to all extension definitions that are currently opened in Forge. Alternatively, you can select "other..." and manually enter a canonical url.
Mritunjay Dubey (Aug 23 2016 at 05:59):
Hey @Michel Rutten, I am defining an extension, and I am trying to give a pattern as regex for its value. Is it possible to tell a pattern for my expected value, if yes how to do that. Please let me know, I have searched on web, but didn't get a relevant blog/article.
Michel Rutten (Aug 23 2016 at 08:37):
Hello @Mritunjay Dubey Here you can find definition of the property:
http://hl7.org/fhir/elementdefinition-definitions.html#ElementDefinition.pattern_x_
And here is an example from the daf-smokingstatus Observation profile:
<element>
<path value="Observation.code"/>
<!-- ... snip ... -->
<patternCodeableConcept>
<coding>
<system value="http://loinc.org"/>
<code value="72166-2"/>
</coding>
</patternCodeableConcept>
So the pattern specifies that an instance must specify the code from the pattern, and may optionally specify additional codes.
Mritunjay Dubey (Sep 25 2016 at 10:55):
Hello @Michel Rutten , Sorry I am replying after so many days. Actually, I tried forge tool for DSTU2, but I wanted to use it for STU3 to create profiles. So is there is a way to do it, or if there are any alternate solutions, please let me know
Michel Rutten (Sep 25 2016 at 12:03):
Hi @Mritunjay Dubey, once STU3 is final we will upgrade all our tools (Forge, Spark server, http://simplifier.net/ platform). Brian Postlethwaite has already started on updating the underlying FHIR .NET API library to STU3, that's the first important step.
Michel Rutten (Sep 25 2016 at 12:11):
There is a way to create STU3 profiles expressed as DSTU2 StructureDefinitions using the current Forge development build (not released yet), by replacing the validation.zip in the Forge application folder with a custom version. However this is a bit involved and not very user friendly. Unfortunately I don't have a lot of time to provide community support for this hack. But the next Forge update will support this. So if you're comfortable with a bit of hacking, this would be an option. I've no time frame yet for the next update, but probably in a couple of weeks.
Michel Rutten (Sep 25 2016 at 12:14):
BTW we have also been discussing the opposite, so in the future you can use the new STU3 Forge release to create DSTU2 profiles based on STU3 StructureDefinitions. Converting StructDefs from DSTU2 to STU3 format back and forth is quite straightforward and can be accomplished by means of a relatively simple XSL transform. So this is what we're looking at for forward and backwards compatibility
Michel Rutten (Sep 25 2016 at 12:14):
Time permitting, we could even integrate the transformation into Forge and provide an "Export to DSTU2" command.
Mritunjay Dubey (Sep 25 2016 at 14:18):
@Michel Rutten thanks for your inputs. I will give it a try.
Last updated: Apr 12 2022 at 19:14 UTC
