New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DSTU2 xml parsing issues #216

Closed
wdebeau1 opened this Issue Sep 4, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@wdebeau1
Collaborator

wdebeau1 commented Sep 4, 2015

I've found a couple of parsing issues parsing xml files for dstu2.
In the case of identifiers, if the identifier contains

    <type value="MRN"/>

a warning should be logged, as that's not valid (type is now a codeableconcept)

In parsing MedicationStatement, attempting to parse the example at https://www.hl7.org/fhir/2015Sep/medicationstatementexample1.xml.html produces the following error:
Error on file e:\tmp\Fhir\bad\MedicationStatementExample1.xml - DataFormatException at [[row,col {unknown-source}]: [47,5]]: Unknown element 'quantityQuantity' found during parse

In parsing https://www.hl7.org/fhir/2015Sep/familymemberhistory-example.xml.html:
Error on file e:\tmp\Fhir\bad\FamilyMemberHistoryExample.xml - DataFormatException at [[row,col {unknown-source}]: [32,5]]: Unknown element 'onsetQuantity' found during parse

@wdebeau1 wdebeau1 added the bug label Sep 4, 2015

@jamesagnew

This comment has been minimized.

Owner

jamesagnew commented Sep 8, 2015

The first issue is solved. Will check that in shortly.

I don't know about the other two though. The datatype is called SimpleQuantity now, but the field still seems to be called "quantityQuantity" in the spec. I've asked in the implementors chat about that...

@jamesagnew jamesagnew closed this in 0863306 Sep 8, 2015

jamesagnew added a commit that referenced this issue Sep 8, 2015

@jamesagnew

This comment has been minimized.

Owner

jamesagnew commented Sep 8, 2015

This wound up not being so bad after all.. Both parts are fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment