NIST/ONC CCDA validation API

1,311 views
Skip to first unread message

Gary Isaac

unread,
Mar 28, 2017, 1:20:52 PM3/28/17
to Edge Test Tool (ETT)
There are some vendors who are leveraging the NIST ETT API for C-CDA validation. I am assuming that production use of the NIST instance would expose unsecured PHI. Is there any way to install only the MDHT functionality of the ETT so vendors can use the API to hit their own servers? Or, would a developer need to install the full ETT test suite to use the API for CCDA validation?

Nagesh Bashyam

unread,
Mar 29, 2017, 8:29:33 AM3/29/17
to Gary Isaac, Edge Test Tool (ETT)

Gary

 

The vendors can download the Reference C-CDA Validator from https://github.com/siteadmin/referenceccdavalidator

and use it for validation.

 

Out of the box, this allows validation with the C-CDA IG.

If you configure vocabularies, then you can turn on vocabulary validation also.

 

There are a bunch of vendors now using it as part of their internal systems to validate C-CDAs.

 

Please let me know if you need additional information.

 

The APIs can be accessed at :

 

https://ttpds.sitenv.org:8443/referenceccdaservice/swagger-ui.html#/reference-ccda-validation-controller

 

Thanks

Dragon

--
You received this message because you are subscribed to the Google Groups "Edge Test Tool (ETT)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to edge-test-too...@googlegroups.com.
To post to this group, send email to edge-te...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/edge-test-tool/56ea3e9a-d412-494a-b812-67683b2ed6b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Gary Isaac

unread,
Mar 29, 2017, 11:46:08 AM3/29/17
to Edge Test Tool (ETT), gary.a...@gmail.com
Thanks for making the reference implementation available.

Gary Isaac

unread,
Mar 29, 2017, 11:56:11 AM3/29/17
to Edge Test Tool (ETT), gary.a...@gmail.com
I have a follow up question about vocabularies. The test procedure states that systems are supposed to validate vocabularies. I do not see any test cases for vocabulary checking such as a CVX code or SNOMED code being invalid. So, are we testing only vocabulary related items like ethnicity codes?

This is a roundabout way to ask if the Test Proctor needs to verify that the CCDA API is using the IG with vocab. Does the vendor have to use the reference implementation with vocabulary setting? Or, can they use the default without vocabulary?

Nagesh Bashyam

unread,
Mar 29, 2017, 1:00:00 PM3/29/17
to Gary Isaac, Edge Test Tool (ETT)

Gary

 

There are two levels of vocabulary validation.

 

1.     Vocabulary validation following the vocabularies and value sets listed in the C-CDA IG and required by the regulation.

2.     Vocabulary validation based on the test data provided.

 

If you select any of the certification criteria like b1, b6 etc, you get both of these and the results from the validation.

If you select CCDA_IG_Plus_Vocab option then you get only #1.

If you select CCDA_IG_Only , then neither #1 nor #2 is enabled.

 

Let me know if you have any other questions.

 

Vendors installing locally would typically use “CCDA_IG_Only” if they do not have access to the vocabularies. If they have access then they would select “CCDA_IG_Plus_Vocab”

kunal...@digi-corp.com

unread,
May 17, 2017, 5:44:02 AM5/17/17
to Edge Test Tool (ETT), gary.a...@gmail.com
Hello,
How to  use referenceccdavalidator API with postman (i.e., api testing tool)?

Thanks,
Kunal.

kunal...@digi-corp.com

unread,
May 18, 2017, 2:31:49 AM5/18/17
to Edge Test Tool (ETT)
Hello, 
Please give response. I'm looking forward to your response.

Thanks,
Kunal.

On Wednesday, March 29, 2017 at 5:59:33 PM UTC+5:30, nagesh.bashyam (Dragon) wrote:

Nagesh Bashyam

unread,
May 18, 2017, 9:22:15 AM5/18/17
to kunal...@digi-corp.com, Edge Test Tool (ETT)

I am not sure what the question is.

 

The validator can be downloaded, installed and configured to perform C-CDA IG only validation, C-CDA IG Plus Vocab validation or any of the 2015 criteria validation.

Please let us know if there is a specific question.

 

Thanks

Dragon

 

From: edge-te...@googlegroups.com [mailto:edge-te...@googlegroups.com] On Behalf Of kunal...@digi-corp.com


Sent: Thursday, May 18, 2017 2:32 AM
To: Edge Test Tool (ETT)

Subject: Re: NIST/ONC CCDA validation API

 

Hello, 

Gary Isaac

unread,
May 22, 2017, 3:34:15 PM5/22/17
to Edge Test Tool (ETT), kunal...@digi-corp.com
Hi Kunal,

You need to setup the required parameters in Postman. The CCDA file param requires a form-data param. Something like this in the screenshots below.




Hit "Send", and you can get the response.
Auto Generated Inline Image 1
Auto Generated Inline Image 2

omer khan

unread,
Jun 4, 2018, 5:50:35 AM6/4/18
to Edge Test Tool (ETT)

i am unable to deploy the war file, did not find the vocabulary files.
then i also try to download the code and open in eclipse, and face this error in pom.xml

i also need to confirm that can you provide me any link/video for war deploy instruction

Thanks
Omer
6-4-2018 2-49-37 PM.jpg

Dan Brown

unread,
Jun 5, 2018, 11:28:28 AM6/5/18
to Edge Test Tool (ETT)
Hi Omer,

The following link contains a readme on how to get vocabulary setup, other documentation, and the valueSets hand created by SITE that we can provide: https://github.com/siteadmin/code-validator-api/tree/master/codevalidator-api/docs
Please combine those documents with the instructions here (follow link and scroll down): https://github.com/siteadmin/reference-ccda-validator and you should be up and running.
Many of the vocabulary files must be obtained manually from VSAC. This is outlined in the referenced documentation.

Pom issue: It looks like you need to import the reference validator dependency projects listed in the pom (content validator and code validator), and subsequently, build them with maven so they are available in the local maven repo. The dependency projects listed are located in the SITE github (https://github.com/siteadmin/code-validator-api and https://github.com/siteadmin/content-validator-api). But, this is not necessary for deploying a pre-built war from the latest reference validator build (https://github.com/siteadmin/reference-ccda-validator/releases/tag/1.0.31).

Thanks,
Dan
Reply all
Reply to author
Forward
0 new messages