Closed jjwdesign closed 5 years ago
Yeah, the current version does not have a way to handle extended json attributes on a "primitive container" type.
The refactor version is being designed with these specific use-cases in mind for both serialization and unserialization purposes.
XML should work just fine, however.
@jjwdesign: could you please try the latest output from v1.0 and see if this addresses the issue for you?
Closing as I believe this to be resolved.
First, thank you very much for this excellent project. This has saved people thousands of hours of development time!
I was trying to work with the Cerner API (Sandbox) at https://fhir-open.sandboxcerner.com/dstu2/0b8a0111-e8e6-4c26-a91c-5069cbc6b1ca - it's an open sandbox. It used the DSTU2 standard. When trying to retrieve Person and Patient data I was seeing a notice that the "_value" property could not be mapped.
I know it's just a notice, so it shouldn't be effecting production. In case anyone else see's this error, you could skip the parameter using the switch statement. Just a quick fix. I'm sure there's a better way of handling this issue.
switch($k) { case 'resourceType': case '_value': continue 2; case 'fhir_comments': continue 2; }