Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update tech-standards.html.erb #36

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update tech-standards.html.erb #36

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 3 additions & 6 deletions source/resources/tech-standards.html.erb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -110,12 +110,9 @@ section: Resources
<p>A data dictionary is a conversion of the clinical information needed for the use case into logical model data elements.</p>

<p>
The following table shows work-in-progress from a clinical expert group identifying clinical requirements for a use case to provide an initial assessment of a potential cancer patient. The table contains necessary data elements, where the information could be extracted, references to prior work, and results of a survey of the experts regarding the “Relevance to Patients Like Mine” to help prioritize the minimal set of information needed.
To begin to define the data dictionary, the clinical expert group will identify a set clinical requirements for a use case. The <%= link_to("clinical requirements and data dictionary template", "playbook/source/images/Clinical_Data_Requirements_Data_Dictionary_template.xlsx") %> provides an example assessment of a cancer patient and instructions for filling out the template. The spreadsheet Clinfo_NGS contains necessary data elements for the use case, data sources, references to prior work, and under the "Use Case Relevance" column a expert assessment of “Relevance to Patients Like Mine” to help prioritize the minimal set of information needed. A blank spreadsheet for clinical requirement development can be found in the Clinfo_Template spreadsheet.
</p>

<p class="alert alert-warning">Image is placeholder only - will replace with accessible table</p>
<p><%= image_tag 'clinical-info-survey.png', :width => '80%', :class => 'py-5' %></p>

<p>
Once information needs have been prioritized, the group should consider whether the data elements should be: </p>
<ul>
Expand All @@ -131,9 +128,9 @@ section: Resources
</ul>

<p>
The group can next develop the data dictionary - a "Rosetta Stone" that defines data elements mapped to the clinical information requirements
The group can next develop the data dictionary - a "Rosetta Stone" that defines data elements mapped to the clinical information requirements. An example data dictionary and a blank template can be found in the <%= link_to("clinical requirements and data dictionary template", "playbook/source/images/Clinical_Data_Requirements_Data_Dictionary_template.xlsx") %> in the DEDToClinfo_Example and DEDToClinfo_Template spreadsheets respectively.
</p>
<p><%= image_tag 'rosetta-stone-table.png', :width => '100%', :class => 'py-5' %></p>


<h3>Common Challenges Related to Compiling Clinical Information Requirements and a Data Dictionary</h3>
<ul>
Expand Down