none
CDA/ CCD Schema validation

    Question

  • Hi,

    I tried to squeeze in this question as a part of different thread below..

    http://social.msdn.microsoft.com/Forums/en-US/1940c81e-85f8-4a5c-8009-143341f07017/uploading-clinical-document-through-healthvault-and-programmatically?forum=healthvault

    I have a document which does NOT validate against either CDA R2 (http://xreg2.nist.gov/cda-validation/validation.html).  Strangely, it gets uploaded using shell as a valid CCD document. 

    I could be wrong here - but is not CCD a restriction on CDA R2? 

    To add to it, if I try schema validation against http://developer.healthvault.com/, this document gets validated as a CCD but it does NOT get validated as a CDA. 

    Would really appreciate some insight here.    Is this expected behavior?

    - Rajesh

    Raj HealthVault Developer Tool http://xray.getrealconsulting.com

    Tuesday, December 10, 2013 8:53 PM

Answers

  • It depends. Our schemas for CDA R2 don't include some of the extensions that are available in the CCD schemas. If your file contains those extensions it could validate as a CCD but not a CDA R2. If you could provide me with an anonymous version of the file I might be able to tell you why this would happen. jeffjon 'at' microsoft.com

    Jeff Jones Technical Lead HealthVault Development Team

    Thursday, December 12, 2013 9:37 PM

All replies

  • HealthVault only does schema validation, not semantic validation. It is the calling application's responsibility to ensure that the document meets the semantic rules of the document type that is derived from CDA R2. One exception to this is that the document may pass schema validation but the data won't be reconciled to HealthVault types if they don't follow the semantic rules for a CCD.

    Jeff Jones Technical Lead HealthVault Development Team

    Tuesday, December 10, 2013 10:19 PM
  • I understand that we HV does not do semantic validation - but only schema validation.  Also, in this case I am referring to shell's handing of the document and not programmatic uploads.

    How come a document that is NOT CDA R2 by schema validation get uploaded as CCD document from shell?  Instead, I would expect a document that does not get validated by CDA R2 appear as a generic file when uploaded from shell.  Am I missing something?

    Raj


    Raj HealthVault Developer Tool http://xray.getrealconsulting.com

    Thursday, December 12, 2013 9:28 PM
  • It depends. Our schemas for CDA R2 don't include some of the extensions that are available in the CCD schemas. If your file contains those extensions it could validate as a CCD but not a CDA R2. If you could provide me with an anonymous version of the file I might be able to tell you why this would happen. jeffjon 'at' microsoft.com

    Jeff Jones Technical Lead HealthVault Development Team

    Thursday, December 12, 2013 9:37 PM