CDA Task Force – Tooling Requirements

1. CDA Task Force – Tooling Requirements Knowledge Base • Implementers search for information and answers to questions • Moderator posts answers, example code Forum • Implementers post questions • Experts in the community respond to questions • Moderators monitor and create issue tracking tickets for unanswered questions, or questions that require additional input HL7-specific Searches ONC Meaningful Use Support Portal Issue Tracker • Moderator assigns questions to community SMEs • SMEs answer questions • SDOs approve answers • Moderator posts answer to Forum and Wiki, and closes resolved Issues CDA Task Force Support Infrastructure

2. Meaningful Use Support – Overall Requirements • Scalability – needs to support a variety of subjects, including HL7 standards, Direct, Privacy/Security policies (e.g., HIPAA), ONC S&CC objectives, etc. • Centralized Clearinghouse – content for different technologies will reside at various external locations (e.g., hl7.org, directproject.org, nist.gov etc.) but will need to be searchable from ONC’s portal. • Guiding Principles: • Facilitate implementers “studying for the test” prior to pursuing certification for the Meaningful Use program. • Provide access to self-study materials and guidance for how to acquire advanced levels of support • Portal-based searches should yield results from all applicable sub-domains.

3. Knowledge Base – Desired Capabilities Searching – need to be able to search for specific C-CDA Template Names or OIDs Cross-referencing – it is desirable to easily navigate across related content. External Access – it would be desirable to be able to integrate with a search originating at the broader ONC MU/Standards Testing Support Portal. Access Controls – we need to limit the pool of users who can create content.Anonymous Access – anonymous users should be able to view content within the knowledge base but not submit content.

4. Forum – Desired Capabilities Threaded Discussions – need to be able to track discussions and responses. Categorized Discussion areas – We should be able to shepherd discussions to logical categories to facilitate future search-ability. Moderator administration – ability for Moderator to edit discussions, lock discussions, move threads, delete posts, etc. Searching – Full-Text searching of historical discussions is desirable. Access Controls – role-based privileges to assign access to different groups Anonymous Access – anonymous users should be able to post questions, but must pass a CAPTCHA or similar test. Graphical User Group differentiation – A user should be able to visually distinguish between a member of the general public, a forum Moderator, and HL7 leaders. External Access – it would be desirable to be able to integrate with a search originating at the broader ONC MU/Standards Testing Support Portal.

5. Issue Tracker – Tooling Requirements Access Controls – role-based privileges to assign access to different groups Anonymous Access – anonymous users should have read-only access to current issues being tracked. Customize Issue meta-data – Different attributes should be able to be captured depending on Issue Type. Support multiple attachments per Issue – Ideally this would allow categorization of the type of attachments – e.g., Sample Code vs. Normative Conformance statements, etc. Support cross-linking of disparate Issues Types – Issues of one type may need to be linked to several issues of a different type. Customize Workflow per Issue Type – The workflow process needs to follow different pathways depending on Issue Type. Workflow automation scripting – Automate actions to occur based upon State transitions within configured workflows (e.g., clearing specific attributes, setting default values, updating linked tickets, etc.) Notifications – Robust/customizable email notification capabilities based upon Issue status changes. Searching – Ad-hoc full-text searching of Issues. Reporting – Custom querying and dashboard capabilities (with metrics) are desirable