Stream: dotnet
Topic: FHIR Mapper
Louis Gordon (May 26 2020 at 14:05):
Spending some time looking into VONK FHIR Mapper as a tool for version to version resource mapping in a REST facade approach.
I created a new structure map using an existing structure map. I couldn't use the administration endpoint for this so I just posted the resource using the machine readable value from another tutorial resource.
When I do the transform I get the following operationoutcome error:
"severity": "error",
"code": "processing",
"diagnostics": "The outputtype dateTime is not supported"
Any thoughts? To repro: POST https://vonk.fire.ly/StructureMap/5752511a-bb59-4e91-b8da-b71eef6d5a26/$transform using the body from this sample resource https://simplifier.net/fhirmapper/FakeInpatientDrugChart-example/~json
Alexander Zautke (May 26 2020 at 15:31):
The FHIR Mapper deployed on that endpoint is currently not running the latest version. In the version 0.3.5 (released today) there was a breaking change for the parameter of the dateOp function. If you use 'DateTime' instead of 'dateTime' it will work. The documentation is a bit ahead, sorry for the confusion.
Alexander Zautke (May 26 2020 at 15:31):
I fixed the StructureMap here: https://vonk.fire.ly/StructureMap/test
Louis Gordon (May 26 2020 at 15:38):
Thanks! I came across the update notes so I thought it might have been the case that I was hitting it at a weird time
Alexander Zautke (May 26 2020 at 15:51):
Please feel free to reach out to vonk@fire.ly in case you need assistance to set up your own local version of the FHIR mapper
Louis Gordon (May 29 2020 at 12:55):
Looks like I might need another hand here. I'm getting a 501 response for POSTing a structure map to http://localhost:4080/administration/$convert with the "text/fhir-mapping;charset=utf-8" Content-Type header.
1) I ran through the VONK server setup here:
http://docs.simplifier.net/vonk/getting_started.html
2) Then the FHIR Mapper tutorial here...
http://docs.simplifier.net/mappingengine/index.html
3) I verified that the mapping engine is loaded via the structure map transform in the capability statement as noted
4) I verified the assemblies are where the article noted, though they were a folder deeper than the version that the article mentions (plugins\vonk.plugin.mapping\0.0.20\Vonk.Plugin.Mapping) they did load
5) I verified the plugins are registered in the pipeline via the output
6) Double checked my SupportedInteractions and PipelineOptions overrides. I'll attach my appsettings.json here as well
appsettings.json
Alexander Zautke (May 29 2020 at 15:02):
I'm sorry for all your trouble to get it working. I added a warning note to the documentation (http://docs.simplifier.net/mappingengine/enginesetup/configuration.html#configure-mapping-engine). Your version (0.3.4 - should be shown in the log when starting Vonk) needs to be configured on the "/" branch, instead of the "/administration" branch.
Alexander Zautke (May 29 2020 at 15:05):
I provide you with the latest version - 0.3.5 - which is not yet included in the offical Vonk distribution. That will then only work on the "/administration" branch
Louis Gordon (May 29 2020 at 15:07):
Yeah looks like the mapping assembly version is 0.3.4.0 as you've noted, I am trying to run with Vonk version 3.6.0.0 currently according to the output
Last updated: Apr 12 2022 at 19:14 UTC
