0% found this document useful (0 votes)
713 views6 pages

Chapter 5 Case Study - New Century Health Clinic

This document provides details for modeling the information system for a medical practice called New Century. It includes instructions to create a context diagram, data flow diagrams, and data dictionary for key system processes. Specifically, it outlines developing diagrams and listings for appointment processing, payment and insurance processing, report processing, and records maintenance. It also provides an example data dictionary entry and process description for the "Make Appointment" functional primitive as illustration.

Uploaded by

George Ramos
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
713 views6 pages

Chapter 5 Case Study - New Century Health Clinic

This document provides details for modeling the information system for a medical practice called New Century. It includes instructions to create a context diagram, data flow diagrams, and data dictionary for key system processes. Specifically, it outlines developing diagrams and listings for appointment processing, payment and insurance processing, report processing, and records maintenance. It also provides an example data dictionary entry and process description for the "Make Appointment" functional primitive as illustration.

Uploaded by

George Ramos
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

1 Prepare a context diagram for New Century’s information system.

Patient Insurance American


Company Medical
Association

Patient Claim Insurance


Reports Payment
&
Outputs
Patient 0
Payment
New Century CPT Codes
Patient
Inputs Information Provider
Management
Reports
System

Office Provider
Staff Inputs Provider
Office Staff
2 Prepare a diagram 0 DFD for New Century. Be sure to show numbered processes for
handling appointment processing, payment and insurance processing, report processing,
and records maintenance. Also, prepare lower-level DFDs for each numbered process.
3 Prepare a list of data stores and data flows needed for the system. Under each data store, list
the data elements required. The data flows are as follows:
1) Bill
2) Drop-in
3) Hours
4) Drop-in Report
5) Fixed Fees
6) Payment
7) Payment Data
8) Receipt
9) Receipt Data
10) Registration Data
11) Report Data
12) Reports
13) Student Data
14) Variable Monthly Fees

The Data Stores are as follows:

15) Drop-In Data


16) Registration Data

Data Elements for each data store are as follows: (Note that answers may vary here – students
should pick out all the data elements identified in Chapter 3 as existing and should speak to new
elements needed to create “family” bills.

17) Drop-In Data


18) Household Number
19) Student Name
20) Student Number
21) Month
22) Date of Attendance
23) Block Attended
24) Registration Data
25) Household Number
26) Student Number
27) Student Name
28) Monthly Fixed Fees
29) Prepare a data dictionary entry and process description for one of the system’s functional
primitives.
4 Prepare a data dictionary entry and process description for one of the system’s functional
primitives.

Data Dictionary

The data flow diagram is used to represent the functional flow of the system. Though New
Century system is very simple, there is no need of making a logical solution complex, a new
principle can be created using decision table or decision tree. A complete listing of the functional
activities consisting of input and output data flows, have been arranged.

Sample documentation of the above four processes identified in the 0-level diagram are
mentioned below:

PROCESS MAKE APPOINTMENT


Purpose: Schedules A Patients Appointment And Services.
Input Data Flows: Appointment Request
Patient Data
Cpt Fee Schedule
Output Data Flows: Service Data

Appt Data Process Description:


For Each Appointment Request From Patient
Retrieve Patient Number From Patients Verify Patient Number
For Each Cpt Code In Appointment Request
Retrieve Cpt Code From Cpt Fee Schedule
Add/Change/Delete Cpt Code In Scheduled Service Data
Add/Change/Delete Provider Number In Scheduled Service Data
Add/Change/Delete Appointment Number, Appointment Date, Start Time, Patient Number In
Scheduled Appointment Data

Appt Data Process Description:


For Each Appointment Number
Retrieve Household Number From Patients
Retrieve Employer Group Number From Households
Retrieve Ins. Co. Number From Households
For Each Appointment Number In Completed Appointment Data Retrieve Fee From Service
Data
Apply Charge To Households
Apply Provider Charges To Providers
Apply Last Exam To Patients
Apply Fee To Mtd Charges
Add Appointment Number, Appointment Date, Start Time, End Time, Patient Number In
Completed Appointment Data
Add Cpt Code, Provider Number, Fee In Completed Service Data
Delete Appointment Number, Appointment Date, Start Time, End Time, Patient Number In
Completed Appointment Data
Delete Cpt Code, Provider Number In Scheduled Service Data Send Claim To Insurance
Company

PROCESS MODIFY CPT CODE


PURPOSE: Add/Change/Delete an American Medical Association CPT code
INPUT DATA FLOWS: CPT CODES
OUTPUT DATA FLOWS: CPT CODES
PROCESS DESCRIPTION:
For each CPT CODE CHANGE from AMERICAN MEDICAL ASSOCIATION Apply CPT
CODE to CPT FEE SCHEDULE

COMPLETE APPOINTMENT
Purpose: Processes An Appointment That Has Been Completed
Input Data Flows: Employer Data
Provider Data
Household Data
Service Data
Appt Data
Output Data Flows: Claim
Charges
Provider Charges
Service Charge
Service Data

PROCESS MODIFY CPT FEE


Purpose: Add/Change/Delete A Cpt Fee
Input Data Flows: Fee Data
Output Data Flows: Fee Data
Process Description:
For Each Fee Change From Provider
Apply Fee To Cpt Fee Schedule
Other Functional Primitive Processes:

PROCESS PATIENT PAYMENT


Purpose: Process A Payment Received From A Patient
Input Data Flows: Patient Payment
Output Data Flows: Mtd Payments Ytd Payments

PROCESS INSURANCE PAYMENT


Purpose: Process A Payment Received From An Insurance Company
Input Data Flows: Insurance Payment
Output Data Flows: Mtd Payments Ytd Payments

PROCESS CREATE CALL LIST


Purpose: Prepare And Print The Daily Call List That Shows All Patients Who Are To Be Called To Be
Reminded Of Their Appointment
Input Data Flows: Call List Data
Output Data Flows: Call List

PROCESS CREATE APPOINTMENT LIST


Purpose: Prepare And Print The Daily Appointment List That Shows All Patients And Their Scheduled
Services For Each Provider
Input Data Flows: Service Data
Provider Appointment Data
Output Data Flows: Appointment List

PROCESS CREATE REMINDER POSTCARDS


Purpose: Prepare And Print Reminder Postcards For Each Appointment
Input Data Flows: Reminder Postcard Data
Output Data Flows: Reminder Postcard

PROCESS CREATE MAILING LABELS


Purpose: Prepare And Print Patient Mailing Labels
Input Data Flows: Mailing Label Data
Output Data Flows: Mailing Labels

PROCESS CREATE STATEMENT


Purpose: Prepare And Print Monthly Statements To Patients
Input Data Flows: Statement Data
Output Data Flows: Statement

PROCESS MODIFY PATIENT


Purpose: Add, Change, And Delete Patient And Household Data Received From Patients
Input Data Flows: Patient Change
Output Data Flows: Patient Update

PROCESS MODIFY HOUSEHOLD


Purpose: add, change, and delete household data changes received from patients
Input data flows: household change
Output data flows: household update

You might also like