More cleanup

source/casestudies/mcode_codex.html.erb

@@ -61,25 +61,26 @@ theme: casestudy
 
       <h3>What is the mCODE Standard?</h3>
       <p><%= link_to("mCODE","https://confluence.hl7.org/display/COD/mCODE") %> is an HL7 <strong><em>standard</em></strong> <%= link_to("FHIR Implementation Guide (IG)","https://hl7.org/fhir/us/mcode/index.html") %> integrating an agreed, core set of common data elements for cancer. These data elements are deemed valuable to patients and other stakeholders via multiple use cases, potentially available in every electronic health record for cancer patients, and machine computable. mCODE consists of approximately 30 FHIR profiles and roughly 100 data elements organized into six thematic groups (see below): Patient Information, Health Assessment, Genomics Group, Disease Characterization, Cancer Treatments, and Outcomes.</p>
-      <figure>
+      <figure class="small-figure">
         <%= image_tag 'mcode-cancer-ring.png', :width => '600', :class => 'py-3', :alt=>"Diagram of cancer treatment stakeholders" %>
         <figcaption>Diagram of oncology stakeholders and categories of related data elements in the mCODE FHIR standard</figcaption>
       </figure>
       <h3>What is the CodeX Community?</h3> 
       <p><%= link_to("CodeX","https://confluence.hl7.org/display/COD/CodeX+Home") %> is a member-driven HL7 FHIR Accelerator hosting a growing <strong><em>community</strong></em> working together to drive substantial improvements around the most important challenges facing specialty health care and research. Initial <%= link_to("CodeX Use Cases","https://confluence.hl7.org/display/COD/CodeX+Use+Cases") %> (projects) focused on improving, collecting, and sharing mCODE-based data in the oncology space.  Through 2024, cardiovascular and genomics Communities have also started work within CodeX.</p>
-      <p>The following graphic summarizes a core CodeX strategy: Enabling all patient data to be collected once, and then shared and used (as consented by the patient) for many different use cases.</p>
-      <figure>
-      <%= image_tag 'codex-vision.png', :width => '700', :class => 'py-3', :alt=>"Diagram of data exchange between cancer treatment stakeholders" %>
-      <figcaption>CodeX vision that a cancer patient's data can be collected once and more easily shared for multiple use cases, provided the data are standardized.</figcaption>
+      <p>The following graphic summarizes a core CodeX strategy: Enabling all patient data to be collected once and then shared and used (as consented by the patient) for many different use cases.</p>
+      <figure class="small-figure">
+        <%= image_tag 'codex-vision.png', :width => '700', :class => 'py-3', :alt=>"Diagram of data exchange between cancer treatment stakeholders" %>
+        <figcaption>CodeX vision that a cancer patient's data can be collected once and more easily shared for multiple use cases, provided the data are standardized.</figcaption>
+      </figure>
       <hr>
       <h2 id="how_it_started">Getting Started</h2>
       <p>(Key Playbook Track: <%= link_to("Community Building", "/playbook/community.html") %>)</p>
       <div class="row">
         <div class="col-lg-6">
           <h3>History 2017-2018</h3>
           <p><strong>Origin:</strong> The lucky spark was a chance encounter between former medical colleagues, Dr. Jay Schnitzer and Dr. Monica Bertagnolli, on an airplane in 2017. Bertagnolli was a preeminent cancer surgeon at Brigham and Women’s and was leading the American Society of Clinical Oncology (ASCO) and Alliance for Cancer Trials in Oncology (ACTO). Dr. Schnitzer was Chief Medical Officer and Chief Technology Officer at MITRE, with a growing portfolio of health information technology research.</p>
-          <p>Drs. Bertagnolli and Schnitzer had been circling around how to achieve a Learning Health System, where caring for every patient enables learning from every patient. Every person with any disease should have access to high-quality care, and also will have the opportunity for their experience to help others in the future. </p>
-          <p>Drs. Bertagnolli and Schnitzer had also been circling around one of the fundamental challenges to achieving a Learning Health System: Lack of a single standard for collecting and sharing patient data electronically. They organized the first clinical requirements team convened under the auspices of ASCO. This team was co-chaired by Drs. Jim Chen and Doug Blaney, and staffed with world-class experts from across the oncology space. The team's mandate was to agree on first use cases (a narrow scope was important), and on a minimal set of clinical data to address use case requirements. This data dictionary later seeded a new standard for cancer data: the <%= link_to("minimal Common Oncology Data Elements","https://confluence.hl7.org/display/COD/mCODE") %>. </p>
+          <p>Drs. Bertagnolli and Schnitzer had been circling around how to achieve a Learning Health System, where caring for every patient enables learning from every patient. Every person with any disease should have access to high-quality care and have the opportunity for their experience to help others in the future. </p>
+          <p>Drs. Bertagnolli and Schnitzer had also been circling around one of the fundamental challenges to achieving a Learning Health System: Lack of a single standard for collecting and sharing patient data electronically. They organized the first clinical requirements team convened under the auspices of ASCO. This team was co-chaired by Drs. Jim Chen and Doug Blaney, staffed with world-class experts from across the oncology space. The team's mandate was to agree on first use cases (a narrow scope was important), and on a minimal set of clinical data to address use case requirements. This data dictionary later seeded a new standard for cancer data: the <%= link_to("minimal Common Oncology Data Elements","https://confluence.hl7.org/display/COD/mCODE") %>. </p>
         </div>
         <div class="col-lg-6">
           <h3>Learnings</h3>
@@ -314,7 +315,7 @@ theme: casestudy
       <p>(Key Playbook Tracks: <%= link_to("Implementation & Testing", "/playbook/implementation.html") %>, <%= link_to("Adoption & Value", "/playbook/adoption.html") %>)</p>
       <p>In less than 5 years, the CodeX Community and other adopters have demonstrated the value of levering the mCODE standard for data collection and sharing to the point where an increasing number of oncology stakeholders are seeing potential value and requesting support from vendors. As of early 2024, there are numerous examples of success.  </p>
       <h3>Vendor Adoption</h3>
-      <figure>
+      <figure class="small-figure">
         <%= image_tag 'industry-implementing-codex.png', :width => '600', :class => 'pt-3', :alt=>"Industry adoption of CodeX infographic" %>
         <figcaption>Infographic showing industry adoption of CodeX standards (2024). Numbers are based on what the team has heard directly. There may be additional independent efforts adopting the CodeX FHIR standards.</figcaption>
       </figure>
@@ -336,7 +337,7 @@ theme: casestudy
       	<li><%= link_to("ONC’s","https://www.healthit.gov") %> US Core Data for Interoperability <%= link_to("(USCDI) + Cancer","https://www.healthit.gov/topic/interoperability/uscdi-plus") %> is aligned with mCODE</li>
       	<li><%= link_to("ONC","https://www.healthit.gov") %> included select mCODE data elements in their USCDI+ proposed Quality Data Element List</li>
       </ul>
-      <figure>
+      <figure class="small-figure">
         <%= image_tag 'mcode-outcome-boxes.png', :width => '600', :class => 'pt-2', :alt=>"Box diagram showing CodeX adoption metrics" %>
         <figcaption>Box diagram highlighting adoption metrics for CodeX and mCODE</figcaption>
       </figure>

source/index.html.erb

@@ -37,7 +37,7 @@ theme: home
 
       <p>Questions that a new specialty should ask themselves before embarking on the above tracks are included on the <%= link_to("Before Starting", "/playbook/getting_started.html") %> page. </p>
 
-      <p><%= link_to("Design Principles", "/playbook/design_principles.html") %> are a foundation for efficient development of quality standards, and will help ensure alignment between different standards development initiatives within and across specialty communities.</p>
+      <p><%= link_to("Design Principles", "/playbook/design_principles.html") %> are a foundation for efficient development of quality standards and will help ensure alignment between different standards development initiatives within and across specialty communities.</p>
 
       <p>A downloadable <%= link_to("Playbook Checklist", "/Files/Playbook-Checklist.docx") %> will help specialty communities embark on new standards initiatives across Playbook tracks.</p> 
 

source/playbook/community.html.erb

@@ -19,7 +19,7 @@ theme: playbook
       <p>Actions that <%= link_to("CodeX","https://confluence.hl7.org/display/COD/CodeX+Home") %> has found indispensable in establishing and building a community include (a) engaging champions, (b) establishing governance, (c) enabling growth, and (d) communicating value propositions.</p>
       <div id="champions">
         <h2>Champions</h2>
-        <p>Identifying speciality champions is an essential first step when starting a new specialty initiative or starting a new use case within that initiative. In CodeX, successful champions are organizations and individuals that:</p>
+        <p>Identifying specialty champions is an essential first step when starting a new specialty initiative or starting a new use case within that initiative. In CodeX, successful champions are organizations and individuals that:</p>
         <ul class="value-list">
           <li><b>Commit to leading</b> the initiative and/or use case</li>
           <li><b>Know</b> the challenges and opportunities (leading to potential use cases), organizations, people, and related initiatives within the larger specialty community</li>
@@ -60,7 +60,7 @@ theme: playbook
       <div id="value_prop">
         <hr>
         <h2>Value Propositions</h2>
-        <p>To grow the community required for a standards initiative to succeed, it is important to understand and communicate the value propositions for different stakeholder groups. Further, stakeholder value should be bidirectional and framed as: (a) How can the standards initiative provide value to stakeholders?, and (b) How stakeholders provide value to the standards initiative?</p>
+        <p>To grow the community required for a standards initiative to succeed, it is important to understand and communicate the value propositions for different stakeholder groups. Further, stakeholder value should be bidirectional and framed as: (a) How can the standards initiative provide value to stakeholders, and (b) How stakeholders provide value to the standards initiative?</p>
         <p>Below are value statements, looking in both directions, for six stakeholder groups:</p>
 
         <div class="community-growth-items">
@@ -133,8 +133,8 @@ theme: playbook
           <h4>Vendors (EHR and other health IT companies)</h4>
           <p class="stakeholder-value">How can the standards initiative provide value to vendors? </p>
           <ul class="value-list">
-            <li>Vendors can help align customer interests, and thus reduce their level of effort on custom implementations.</li>
-            <li>They can provide input to ensure standards are implementable in their systems and consistent across specialties, reducing costs asscoatied with development and maintenance.</li>
+            <li>Vendors can help align customer interests and thus reduce their level of effort on custom implementations.</li>
+            <li>They can provide input to ensure standards are implementable in their systems and consistent across specialties, reducing costs associated with development and maintenance.</li>
             <li>Vendors who participate actively have a first-mover advantage that can provide a competitive advantage.</li>
           </ul>
 
@@ -187,10 +187,6 @@ theme: playbook
 
       </div>
     </div>
-    <div class="playbook-bottom-navigation">
-      <div class="previous">  <%= link_to("Prev: Design Principles", "design_principles.html", :class=>"btn btn-outline-primary btn-lg") %></div>
-      <div class="next"><%= link_to("Next: Use Cases & Planning", "use_cases_planning.html", :class=>"btn btn-outline-primary btn-lg") %></div>
-    </div>
   </div>
 </div>
 

source/playbook/design_principles.html.erb

@@ -45,7 +45,7 @@ theme: playbook
           </ul>
         </li>
 
-       <li>How clinical requirements are represented in <b><%= link_to("FHIR Implementation Guides (IG)", "standards.html#fhir_ig_development") %></b> influence their useability, and their interoperability across specialties.
+       <li>How clinical requirements are represented in <b><%= link_to("FHIR Implementation Guides (IGs)", "standards.html#fhir_ig_development") %></b> influence their useability, and their interoperability across specialties.
           <ul>
            <li>Develop first a <b>single, core IG</b> that represents the minimal clinical requirements for small set of use cases concepts common within the specialty. This core IG can be improved upon as use cases are executed and supplemented within related IGs when data requirements are important for just a small subset of the community.</li>
           <li>Leverage <b>government-backed interoperability standards</b> whenever possible, e.g., <a href="https://www.healthit.gov/isa/united-states-core-data-interoperability-uscdi">United States Core Data for Interoperability (USCDI)</a>, <a href="https://hl7.org/fhir/summary.html">Fast Healthcare Interoperability Resources (FHIR)</a>, <a href="https://www.hl7.org/fhir/us/core/">US Core FHIR Implementation Guide</a> for core patient data, and others.</li>

source/playbook/use_cases_planning.html.erb

@@ -35,7 +35,7 @@ theme: playbook
 			<p>Below are key learnings around the CodeX use case discovery and planning stages. The CodeX "execution" experience will be referenced in the <%= link_to("Implementation & Testing","implementation.html") %> and <%= link_to("Adoption & Value","adoption.html")%> sections of this website.</p>
 			<hr>
 			<h2 id="use_case_discovery">Use Case Discovery:<br>Identifying and Prioritizing Potential Specialty Projects</h2>
-			<p>Use case discovery, in CodeX, generally starts with champions who engage and gain commitment from potential participants. Together, they identify and priortize use cases projects, based in part on the factors below.</p>
+			<p>Use case discovery, in CodeX, generally starts with champions who engage and gain commitment from potential participants. Together, they identify and prioritize use cases projects, based in part on the factors below.</p>
 			<p>New specialties should review <%= link_to("CodeX oncology use cases","https://confluence.hl7.org/display/COD/CodeX+Use+Cases") %> to identify parallel use cases (e.g., for clinical trials, registry reporting, quality measurement, prior authorization, and others that cut across specialties) which could jump start their own specialty use cases. Modeling new specialty work after existing work can streamline development and ensure compatibility with prior efforts, thus improving implementer, health system, and patient experiences.</p>
 
 			<p>For the CodeX Program Management Office to assess the readiness of a use case to go into the CodeX Discovery Stage, the following information is requested:</p>
@@ -103,7 +103,7 @@ theme: playbook
 						<li>Are there additional personnel, facilities, and/or financial resources required to succeed, that are not committed yet?</li>
 						<li>Think about the types of resources needed over the entire project, through planning, development, implementation, testing, and adoption.</li>
 						<li>Describe the options and plans for attaining necessary resource. It can be difficult to estimate resource needs accurately, especially in the early phases of a use case. Note that use case scope and schedule can be adjusted to the availability of resources.</li>
-						</li>Provided on this site is a <%= link_to("Role and Resource Planning speadsheet template", "/Files/Use-Case-Roles-and-Resource-Planning.xlsx") %> (download) which can help define resource requirements and fulfillment.</li>
+						</li>Provided on this site is a <%= link_to("Role and Resource Planning spreadsheet template", "/Files/Use-Case-Roles-and-Resource-Planning.xlsx") %> (download) which can help define resource requirements and fulfillment.</li>
 					</ul>
 				</li>
 

source/resources/index.html.erb

@@ -32,7 +32,7 @@ directory_index: false
           <p>Resources that new specialty standards initiatives can use for more efficient work.</p>
           <p><%= link_to("Playbook Checklist", "/Files/Playbook-Checklist.docx") %> of the most important steps across all five Tracks (download)</p>
           <p><%= link_to("Community charter template", "/Files/Standards Community Charter Template.docx") %> (download)</p> 
-          <p><%= link_to("Role and resource planning speadsheet", "/Files/Use-Case-Roles-and-Resource-Planning.xlsx") %> (download)</p>
+          <p><%= link_to("Role and resource planning spreadsheet", "/Files/Use-Case-Roles-and-Resource-Planning.xlsx") %> (download)</p>
           <p><%= link_to("Data Dictionary Template spreadsheet", "/Files/Clinical_Data_Requirements_Data_Dictionary_template.xlsx") %> (download)</p>
           <p><%= link_to("SVG Tool", "https://www.drawio.com/") %> used for <%= link_to("creating interactive diagrams", "https://ciscodevnet.github.io/graphyte/diagrams_drawio/") %> like the <%= link_to("mCODE conceptual data model diagram","https://hl7.org/fhir/us/mcode/") %></p> 
         </div>
@@ -54,7 +54,6 @@ directory_index: false
               </ul>
             </section>
 
-
             <section> 
               <h4><%= link_to("Use Cases & Planning", "/playbook/use_cases_planning.html") %></h4>
               <ul>