Instructions
Follow the script instructions and record the information in the designated table cells. You may wish to make notes below the questions.
Pre Interview:
Item |
Information/Response |
---|---|
Date: |
12/18/2009 |
Requirement # unique id <SemCon Ops Initiative>.<analysts initials><requirement number> |
Init1pm17 |
Originator/Customer's Name: |
|
Originator/Customer's Company: |
NCI |
Summary of requirement pre-interview, by Reviewer: |
The US Health Information Knowledgebase (USHIK) is the Agency for Healthcare Research and Quality's (AHRQ) metadata registry of the data elements and their characteristics from the standards that the HHS Secretary has endorsed, adopted, and recognized. This includes data elements from HIPAA transaction standards, Consolidated Health Informatics domains standards, and HITSP interoperability specifications. Since NCI and caBIG will be required to comply with the standards described in USHIK, our new semantic infrastructure must be capable of easily consuming information from the USHIK resource as static semantic content. |
Recommended Next Step Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room |
Followup Interview |
Post Interview - ongoing throughout development of use cases:
Item |
Description |
Information/Response |
---|---|---|
Stakeholder Community: |
Enter appropriate category of stakeholder from Primary Stakeholders:
|
|
Requirement Type (required) |
Analyst's assessement of the most appropriate category/type of requirement (no need to ask interviewee):
|
|
ConOp Initiative(s) |
|
|
High Level Use Case Summary) |
Please write a short descriptive narrative use case. |
|
Use Case Linkage (required) |
Which use case(s) is this requirement linked to? (should follow Use Case numbering scheme <SemCon Ops Initiative>.<analysts initials><requirement number>.<use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc. |
Use case Number(s): |
Conflicts / Dependencies(required) |
Are there any conflicts with other requirements / use cases? |
Yes OR No - If yes, what and why? |
Next Step (required) |
After reviewing the results of the interview, the forum, and all other materials related to this requirement, the analyst should recommend the next step, then attach the Tiny Link (on the Info tab) for this page to the Master List table. |
Enter one: Follow-up interview, Observe, Use Case Template (text), Use Case Model (formalized/UML diagram), Group Discussion, Prototype, Waiting Room |