We also are seeing may places where the referenced resources are not being returned in the searchset bundle even through we have used the _include ExplanationOfBenefit:* - GET [base]/ExplanationOfBenefit?[parameter=value]&_include=ExplanationOfBenefit:* search parameter.  The return code is 200 OK, so the Server thinks and is projecting that the query was executed correctly, but in fact, it was not.  The searchset Bundle is incomplete. 

Slide 9 of the attached ppt deck shows all the missing Provider references that were missing from the searchset Bundle. Is Aegis producing tools to validate these returned Bundles?  We need to give Servers a better way to see these problems.  I think we need better testing tools for Servers prior to the April Connectathon.  These problems are going largely undetected, and if we don’t have a way of rejecting poor quality EOB data, then Servers won’t get better.  (This will be like watching the CDA movie all over again….low capability to validate the output leading to the industry thinking something better isn’t possible, when in fact something better is possible if we just expect it to be., and make validation tools that are easy to access and use so issue like this can be readily detected and understood.)  We need to nip this in the bud ASAP.