Before a CDS artifact is made public, the project team will review the submission and contact you to discuss any changes that might be needed. Saving your artifact as “Needs Review” rather than “Draft” will begin this process.

NOTE: Take the additional step of contacting the CDS Connect project team at cds-connect-feedback-list@groups.mitre.org or by using the “Contact CDS Connect” button on the User Account home page.

You can expect the review to include:

1. Examination of the “Needs Review “ version to see which data fields have been populated, which fields are missing, and if any of the fields have been misused.
2. Review of any technical support document(s), such as implementation guides. The team will review the content of the document(s) and check the file for 508 accessibility. They may share any glaring errors (e.g., spelling errors, dead hyperlinks, missing references) or share suggestions on how to improve the document(s).
3. A clinical review of evidence source(s) and how the CDS implements them. This is a high-level review of evidence source and the logic of the artifact.
4. Technical review of logic and test files attached to artifact.
   • When possible, files will be compiled and run on the supplied CDS test cases.
   • Review of the way standards [ (e.g., Fast Healthcare Interoperability Resources (FHIR), Clinical Quality Language (CQL),  SMART, etc.)] are applied within the CDS. The team may send feedback on glaring errors (e.g., CDS that will not compile or run, missing files, missing value sets, etc.) and provide a list of suggested improvements.