Hospital Abstracting Data Flow Diagram
The hospital abstracting data flow diagram shows the detailed procedural flow of control of the function. A text description of the diagram and legend may be found below. For information about reading diagrams, see Diagram Conventions.
HDFD 1.5 - NPCR AERRO: Perform Abstracting Data Flow Diagram
Version 1.0 Revised: 4-8-2010
- Block 1: Steps 1 to 3
Step 1. The process begins with processing event reports that contribute to a reportable cancer case. Step 2. The registrar selects a new reportable cancer case ready to be abstracted. (BR01) Step 3. Cancer registry (CR) software processes any pending reports for this case by performing casefinding and passive follow-up (HUC 1.4).
- Block 2: Steps 4 to 5
Step 4. CR software creates and automatically populates a new cancer abstract with data items for the event reports in the ToBeAbstracted table. (BR02) (SR01, SR02, SR03) Step 5. CR software displays event reports for registrar review. (SR04, SR05, SR06)
- Block 3: Steps 6 to 7
Step 6. The registrar reviews event reports, validates data items that were populated automatically, and inserts new information in the abstract. If more than one new cancer requires abstracting, CR software creates and automatically populates a second abstract and the process continues with Step 6. If an event report has an error or is incomplete, the registrar notifies the data source and the process continues with Step 5.6. (BR03, BR06, BR07, BR08, BR09) (SR07, SR08, SR09, SR10, SR11, SR15, SR16) Step 7. The registrar determines the level of completion and sets the status flag, and the CR software timestamps it. (BR04) (SR12)
- Block 4: Steps 8 to 10
Step 8. CR software sets reporting/end-point triggers. (BR05) (SR13) Step 9. CR software electronically files documents in the MatchedEventReports table. (SR14) Step 10. The process ends.
Data Flow Diagram Legend
There are two actors: the registrar and cancer registry (CR) software.
The process starts when the registrar selects a new reportable cancer that is ready to be abstracted. The CR software checks whether event reports for these cases are waiting for review of reportability by the registrar. If there are event reports to be reviewed, the registrar reviews them to decide if they are reportable. If it is a reportable cancer, the CR software creates and auto-populates a new cancer abstract from the event reports in the TobeAbstracted table. If the event report is not a reportable cancer, the software updates the follow-up information on the CR record and stores the event report in the MatchedEventReports table. If the registrar cannot decide if it is a reportable cancer, the CR software stores the event report in the PendingInformation table and the registrar sends e-mail to the appropriate personnel to determine reportability; when the registrar receives a response, he or she reviews the report again to decide reportability.
The new cancer abstract created from the event reports in the ToBeAbstracted table is displayed for registrar review. The registrar reviews the event report to determine if more than one new abstract is required. If required, the CR software creates and auto-populates a new abstract. If no new abstract is required, the registrar checks the abstract to see if populated data are correct. If the data are not correct, the registrar revises the incorrect data and notifies the data source about the incorrect data. If the data are correct, the registrar checks data completeness. If the data are not complete, the registrar requests more information from the data source; when the registrar receives a response, he or she reviews the abstract again for reportability and completeness. If the data are complete, the registrar determines the completion level and sets the status flag and timestamp for the abstract. The CR software sets the reporting and end point triggers and stores information in the MatchedEventReports table, and the process stops.
Business Rules (BR)
For details of the business rules and software requirements, please refer to the Hospital Abstracting Use Case [PDF-392KB].
- BR01 applies to CR software identifying new reportable cancer cases ready to be abstracted.
- BR02, BR03, and BR04 apply to creation and auto-population of a new cancer abstract with event reports in the ToBeAbstracted table.
- BR07, BR08, and BR09 apply to determining the reportability and completeness of event report.
- BR05 and BR06 apply to determining completion level and setting status flags, timestamps, and reporting and end point triggers.
Software Requirements (SR)
- SR01, SR02, and SR03 apply to creation and auto-population of a new cancer abstract with event reports in the ToBeAbstracted table.
- SR04, SR05, SR06, and SR07 apply to determining whether more than one new abstract is required.
- SR08 applies to determining the completeness and setting the status flag and timestamp for event reports.
- SR09 applies to electronic filing of documents.
- SR10 applies to determining reportability of the event report.