4.
Identify the messages that you will send or receive
Identify the message bundles to be implemented by reviewing the Toolkit Service Listing Spreadsheet. Once you have determined the relevant message bundles, download the appropriate message specifications from the TRUD website as mentioned in Step 2.
For example, if after reviewing the Service Listing Spreadsheet you have determined that the Non-Coded CDA document is the service you will be implementing support for, download the Non-Coded CDA Message Domain Message Specification from TRUD. It contains the details of message definitions and interactions required to support the roll-out of Non-coded CDA Document.
7.
Evidence submission
The Supplier Certified Requirements Coverage spreadsheet forms the central hub of conformance submissions. This provides you with a list of in-scope requirements and test cases that your implementation has to meet to gain conformance.
By following the instructions provided in the spreadsheet you will record the system type, ITK message Bundle(s) and the Transport (all established in earlier steps) and filtering the spreadsheet. You must make a statement against each in-scope requirement, providing either a link to physical evidence or a self-certified statement which should all form part of the submission to the ITK Conformance Team.
All ITK conformance submissions are managed on a "first come first served" basis. On receipt of a submission the ITK Conformance Team will review and provide feedback. If further evidence or expansion of statements is required this will be processed in an iterative way until completion.
Last edited: 1 October 2019 12:24 pm