Generated Content, Images and FHIR Shorthand Files

input/pagecontent/use_cases.md

@@ -34,7 +34,7 @@ This use case is supported by the following
 
   - [Produce Measure](transaction-2.html)
 
-#### Collecting Hospital and Ventilator Measures Process Flow
+#### Collecting Hospital and Ventilator Measures Process Flow 
 
 Measure report data can come from multiple systems within a facility. For example, the CDC/NHSN Patient Impact
 and Hospital Capacity Module asks for the following data elements:
@@ -81,7 +81,7 @@ a report on ICU beds and equipment, including ventilated patients in ED/Overflow
 Total ICU Beds, Occupied ICU Beds, Total Ventilators, Ventilators in Use.
 
 
-
+   
 1. The system collects information about ventilators outside the ICU for which the associated patient
 was admitted for suspected or confirmed COVID-19. It can makes the determination of suspected/confirmed COVID-19 from
 the DG1 segment of the ADT message it recieved regarding the patient.
@@ -107,7 +107,7 @@ examining messages recieved and data in its database, and then reports these to
 within the hospital.
 
 
-
+   
 1. The Bed Management System examines master file data to count the total number of beds in the hospital,
 as well as those beds specifically identified as being for acute (inpatient) care. The Bed Management solution can be a
 component
@@ -128,7 +128,7 @@ on multiple data elements
    The Hospital's EHR collects data for multiple data elements.
 
 
-
+   
 1. The EHR collects data on hospitalized patients w/ COVID-19.
 2. The EHR collects data on hospitalized patients diagnosed with COVID-19 14 days after admission.
 3. The EHR collects data on patient deaths due to COVID-19.
@@ -181,7 +181,7 @@ This use case is supported by the following
 
   - [Communicate Results](transaction-1.html)
 
-#### Accessing Measure Reports Process Flow
+#### Accessing Measure Reports Process Flow 
 
 In this use case, we see the classic "dashboard" panel, where a public health user
 selects a region, and one or more measures (or functions of measures) to report on, and the data is presented
@@ -257,7 +257,7 @@ This use case is supported by the following
 
   - [Query Measure Definition](transaction-1.html)
 
-#### Distributing Measure Definitions Process Flow
+#### Distributing Measure Definitions Process Flow 
 
 Measures created for tracking a public health emergency may be revised periodically to support changing needs. This
 use case supports the need
@@ -275,7 +275,7 @@ to distribute updated measure definitions to organizations who report on these m
 agencies to identify reporting requirements.
 
 
-
+   
 
 1. <html:span xmlns:html="http://www.w3.org/1999/xhtml" id="BED-STEP5">Return matching measure specifications</html:span>
 
@@ -295,8 +295,6 @@ This use case is supported by the following
 
   - [Measure Consumer](actors.html#measure-consumer)
 
-  - [Measure Definition Source](actors.html#measure-definition-source)
-
   - [Measure Definition Consumer](actors.html#measure-definition-consumer)
 
   - [Measure Computer](actors.html#measure-computer)
@@ -307,7 +305,7 @@ This use case is supported by the following
 
   - [Compute Measure](transaction-1.html)
 
-#### Automating Measure Computation Process Flow
+#### Automating Measure Computation Process Flow 
 
 Automating measure reporting reduces the burden on users for manual data collection. When a measure has been
 automated, it
@@ -367,7 +365,7 @@ This use case is supported by the following
 
   - [Compute Measure](transaction-1.html)
 
-#### Reporting Supplemental Data Process Flow
+#### Reporting Supplemental Data Process Flow 
 
 Supplemental data enables additional data analysis to be performed. The MeasureReport itself provides the capacity
 to detect
@@ -420,3 +418,4 @@ with the measure.
 1. <html:span xmlns:html="http://www.w3.org/1999/xhtml" id="FHIRSupplementalData">Returns Supplemental FHIR Resources</html:span>
 
    The local EHR or FHIR Server returns the supplemental data and included resources.
+