Stream: netherlands
Topic: Announcement -- GitHub for profile development
Alexander Henket (Mar 22 2017 at 20:25):
Hi all. After talks with ZorgDomein and earlier talks with other parties today we, Nictiz/MedMij reached some conclusions that I feel are helpful to share here. We'll be coming back on that next week during the WGM NL as well:
.
We anticipate FHIR to take off in The Netherlands on STU3. STU3 became a fact today at http://hl7.org/fhir. Now that STU3 is live with some last minute polishing going on, it is time for the tools to update. Furore has posted a roadmap for that here https://thefhirplace.com/2017/03/02/simplifier-and-forge-migration-to-stu3/
.
For the first rounds of profiling and to accomodate pilots/kickstarts we have been working on DSTU2. The result of that may be found on Simplifier: https://www.simplifier.net/NL-BasicComponents and https://www.simplifier.net/Nictiz.
.
Theoretically we could start on STU3 profiling when Forge and Simplifier are ready. But that would be May 6 if the roadmap turns out to be accurate. This is difficult to wait for for ZorgDomein, but likely also for IKNL, potentially for people working on preparations for VIPP and what not. So we want to work ahead and this appears possible with a little help of github.com.
.
As of today we'll feverishly be working on getting our development onto GitHub: https://github.com/Nictiz. Here you'll find 4 repositories NL-BasicComponents (DSTU2 / STU3) and MedMij (DSTU2 / STU3). The idea is this:
.
- Development/maintenance is fully out in the open on github (we worked in a closed environment before). This gives you all other features you may or may not already work with such as cloning, pull requests etc.
- A webhook allows publication of changes from github projects to be pushed to Simplifier allowing for assurance that profiles continue to be published as agreed upon. We have no intention of making any change how in we use Simplifier
- The STU3 repositories on GitHub allow for cutting edge access to these profiles. As soon as Simplifier is ready for it, we'll be publishing those there too
.
Some things are not yet worked out. Versioned canonical URLs, specific slicing issues and maybe more as we go, but we really hope to serve the community better by being as open as possible in every step. Input welcome.
@Ben Schrijver, @Theo Stolker, @Marc de Graauw, @Marten Smits, @Ardon Toonstra, @Arianne van de Wetering, @Melle Sieswerda
Ben Schrijver (Mar 22 2017 at 20:43):
Great job on getting things in motion this fast, thanks!
Michael van der Zel (Mar 27 2017 at 09:32):
+1
Marc de Graauw (Mar 27 2017 at 09:40):
I forked https://github.com/Nictiz/NL-BasicComponents-STU3, uploaded STU3 compliant versions and created a pull request. What I haven't done is create fhirpath for constraints. Of course, the decisions needed like canonical URL's, it's just my take, but this should be a decent start for discussion at the WGM.
Alexander Henket (Mar 27 2017 at 12:24):
@Marc de Graauw I've merged your pull request into the master and done initial validation/updates. Marten and Ardon are working on checking/adding the fhirpath expressions (HumanName | Address). They might run into more things I missed. Thanks a Bundle!
Ardon Toonstra (Mar 28 2017 at 08:18):
@Michael van der Zel This morning I restructured the MedMij-DSTU2 repository and added Excel files containing mappings from the ZIBS to FHIR. Before creating the profiles these mappings were made to get an overview. They contain our notes and issues but these may be outdated and cannot be seen as complete. The profiles itself contain a mapping as well: the mapping element is populated with the ZIB’s concepts ID.
Michael van der Zel (Mar 28 2017 at 08:37):
@Ardon Toonstra Thanks. I will use that info for the MedMij ZIB Compliance check. TTY thursday / friday?!
Michael van der Zel (Mar 30 2017 at 07:50):
@Ardon Toonstra I found the xlsx files. Great that mappings for DSTU2 and STU3 are in there, but is it not better to move the xls from the DSTU2 folder one level up?
Last updated: Apr 12 2022 at 19:14 UTC
