Message Validator - RelatedPerson Error

[Braeden Rai]

Hello, 

We were testing the message validator for the Amb Sample 1/Alice Newman patient, and encountered these errors:

Error - 

The scenario contains RelatedPerson data with Relationship:, lastName: , firstName: GPARNT, Rick, Holler , however there is no matching data in the submitted CCDA.

Error - 

The scenario contains RelatedPerson data with Relationship:, lastName: , firstName: SPS, Matthew, Newman , however there is no matching data in the submitted CCDA.

In the attached XML screenshot, it looks like we're sending this information in a valid way, is this an issue with the validator?

[Kim Poletti]

Hi - Thanks for reaching out. This has been logged for review and a member of the team will reach out in the near future.

[Kim Poletti]

Hi Braedon,

Would you please send us the C-CDA you submitted? This will help us investigate the issue.

Thank you,

Kim

[Braeden Rai]

This is the document we submitted. Also, similar errors are occurring for all of the b1 test patients, not just sample 1/Alice Newman. 

[Braeden Rai]

Hello,

Is there any chance you could look at this and let us know if this can be addressed before the next release?

[Kim Poletti]

Hello Braedon,

The team has investigated this and noted that:

1. SITE content validator is looking for name parts (given, family) - example submitted is only including <name> (please use the structure in the attached example).

Our team will update the test data to use code from the latest version of value set in a future release.

[Kim Poletti]

Apologies, please use this sample format instead:

[Braeden Rai]

The sample format uses US Realm Person Name, which allows for the name to be pieced out, or for it to just be a string, which is what our documents do. If we should not be sending just a string, is there a different requirement we should be looking at?

[Kim Poletti]

The technical team confirms you are submitting correctly. We are in the process of updating our files to allow for this format. The fix will be in a future release.