Stream: dotnet
Topic: fhirpath tester
Brian Postlethwaite (Dec 15 2016 at 05:13):
Incase people are interested, I just pushed the source for my FhirpathTester to Github.
Of note in this is concurrent support for DSTU2 and STU3 using the NuGet packages.
Brian Postlethwaite (Dec 15 2016 at 05:14):
This is a reasonable example of a project that includes support for both versions at the same time, and how to resolve which to use.
Brian Postlethwaite (Dec 15 2016 at 05:15):
After adding the 2 packages, you need to update the properties of the 2 references assemblies changing the Aliases property on each from global to either DSTU2 or STU3 (for the appropriate library)
Richard Kavanagh (Dec 28 2016 at 17:47):
Hi @Brian Postlethwaite - I'm running your tester app (unchanged) and am getting the following errors
Richard Kavanagh (Dec 28 2016 at 17:47):
Invalid name character in 'codeOfT<Hl7.Fhir.Model.Narrative+NarrativeStatus>'. The '<' character, hexadecimal value 0x3C, cannot be included in a name.
Richard Kavanagh (Dec 28 2016 at 17:49):
This is with the XML being an Observation example out of DSTU2 and the expression anything that seems to have the Descendants() command.
Brian Postlethwaite (Dec 31 2016 at 06:18):
I'll have a look at that next year!
;P
Brian Postlethwaite (Jan 03 2017 at 00:24):
I just grabbed the example http://hl7.org/fhir/observation-example.xml and it worked fine, which one did you try?
Brian Postlethwaite (Jan 03 2017 at 00:30):
I even tested it with http://hl7.org/fhir/2017Jan/patient-glossy-example.xml and it accurately detects that this resource is STU3 only.
And removing the generalPractitioner from the resource it detects that the resource is valid in both DSTU2 and STU3.
Richard Kavanagh (Jan 04 2017 at 22:36):
Ok - I also used the example http://hl7.org/fhir/observation-example.xml with an expression of Observation.children().
Richard Kavanagh (Jan 04 2017 at 22:38):
Brian Postlethwaite (Jan 04 2017 at 22:53):
Thanks, I can reproduce this too.
Don't know why its doing that. Will look into it.
Brian Postlethwaite (Jan 04 2017 at 23:07):
Thanks Richard, I know what the issue is now.
The tool is confused between STU3 and DSTU2 in this case while outputting the results of the query.
Brian Postlethwaite (Jan 04 2017 at 23:20):
Actually, its more simple than that. The FHIR XML serializer isn't able to handle outputing an XML fragment for the status property alone using:
Hl7.Fhir.Serialization.FhirSerializer.SerializeToXml(t2)
Which gets that exception. So I'll need to work out what the bug in the serializer is.
Brian Postlethwaite (Jan 17 2017 at 05:14):
Ok, have pushed the fix for this issue (thanks Ewout)
Richard Kavanagh (Jan 17 2017 at 16:00):
So the fix is in the core API? I guess it will not get into a nuget for a while though...
Brian Postlethwaite (Jan 18 2017 at 02:19):
Nope, 2 lines in the tester tool itself!
So go fit it using it now. (all pushed and ready for a pull)
Last updated: Apr 12 2022 at 19:14 UTC
