Support with systems diagrams and Rapid Application Development

Lukket Opslået Apr 19, 2007 Betalt ved levering
Lukket Betalt ved levering

I have carried out a search for coders and computer experts on Renta-coder specifically for people who know how to create high level design diagrams and also know about Rapid Application Development (RAD). I would much prefer it if you are expert in both of these fields as it will make working together, much easier.

I am a computer programmer and I have been asked to build a computerised system to handle a small health clinic’s information system for a friend/work colleague. I am an experienced programmer and network administrator but seeing as I am self taught, I haven’t had much experience with drawing systems diagrams so I need some help with some of the more involved diagrams to demonstrate the system configurations. Unfortunately I am working on very tight schedule, so I am looking for someone who can work well and quickly.

Here is some information regarding the health clinic’s systems:

The health clinic staff includes:

* Doctors

* Registered nurses

* Physical therapists

* Office staff workers.

There are various people who run the clinic and their jobs are as follows:

* Office manager

* Office payroll

* Tax reporting

* Profit distribution

* Patient records coordinator

Further information regarding the health clinic's information system is carried on in the 'deliverables' section.

## Deliverables

Since the Health Clinic has decided to computerise its office systems, I have suggested that they should incorporate the patient record system, the patient insurance billing system and the patient scheduling system together due to the fact that there are significant interactions between them. I have been asked to come up with a report to justify this decision. Within this report I have been asked to include the following diagrams to better represent my justification for the 3 systems.

* A context dataflow diagram for the information system.

* A diagram 0 dataflow diagram for the information system.

* Identify possible use cases and actors for the information system.

* Create a use case diagram for the information system.

* Create a use case description document for at least 3 use cases.

I have already completed the above tasks to help support my justification for the computerisation of the 3 systems but I don’t know how to complete the next set of requirements (details below). I need these tasks to be completed so I can fully demonstrate my decisions. If necessary, I can send you the diagrams that I have completed from the previous requirements along with the use case descriptions but they are in a ‘.dia’ format which is why I haven’t included them within this description as not many people have the Dia program on their computer.

These two requirements are the things I need completed:

*· Use either a Process and Data approach or an Object Oriented approach to create a High Level Design for the systems at the Health clinic. Any assumptions needed to make the design should also be documented (I would be obliged if these documentations were done in a text file called [url removed, login to view])*

*· Provide arguments both for and against the use of a Rapid Application Development approach to the systems development of the information systems. Then draw a conclusion as to which approach you would recommend. (This conclusion is up to you, seeing as I haven’t had any experience with ‘Rapid Application Development’. Please make sure that all arguments either for or against the use of RAD are set out in a coherent manner in a word document called RAD.doc.*

Here is a description of the ‘data’ and ‘services’ shared between the various members of the health clinic:

The doctors, nurses and physical therapists provide services and perform various medical procedures. All procedures are coded according to Current Procedure Terminology, which are published by the American Medical Association (AMA).

Seven reports are required at the clinic. The first report is the daily appointment list for each provider. The list shows:

* all scheduled appointment times

* patient names

* services to be performed <UL type=disc> <OL type=1>

* A second daily report is the call list, which shows the patients who are to be reminded of their next day’s appointments. The call list includes the patient name, telephone number, appointment time and provider name.

* The third report is the weekly provider report that lists each of the providers and the weekly charges generated, plus a month-to-date (MTD) and year-to-date (YTD) summary.

* The fourth report is the statement ??" a preprinted form that is produced monthly. The statement header information includes the statement date, head of household name and address, the previous month’s balance, the total household charges MTD, the total payments MTD, and the current balance. The bottom section of the statement lists all activities for the month in date order. For each service performed, a line shows the patient’s name, the service date, the procedure code and description, and the charge. The statement also shows the date and amount of all payments and insurance claims. When an insurance payment is received, the source and amount are noted on the form. If the claim is denied or only partially paid, a code is used to explain the reason. A running balance appears at the far right of each activity line.

The associates also require two insurance reports: the weekly Insurance Company Report and the monthly Claim Status Summary. In addition to these six reports, the office staff would like to have mailing labels and computer-generated postcards for sending reminders to patients when it is time to schedule their next appointment. Reminders usually are mailed twice monthly. (This information was also in the requirements briefing and I thought it helped illustrate what is actually required to a better degree.)

In order to register with the clinic, the staff provides the patient with medical history and insurance billing forms. The patient completes these forms and returns them to the staff. Staff of the clinic then creates a patient file and adds the patient to current list. Patients can also request to update their records in the clinic. They send the clinic staff updated information and the staff locates patient record and updates them.

The patients request the clinic in order to make any appointment. The staff checks the availability and informs the patient. The clinic staff mails postcards and calls patients two days before their appointment. It is also possible that the patient requests a new appointment or change. Then the staff offers available appointments to the patient and then the staff adds appointment and cancels changed appointment if needed.

Insurance claims are carried out by the patient who submits the claims to the clinic. The clinic staff verifies patient the insurance carrier and policy number information. The claims are prepared based on these codes provided. The clinic staff then submits the claim to the insurance carrier. The patients can still make payments to the clinic for other things such as phone bills etc. The staff deducts insurance payments and calculates balance due and then prints the bills and mails them to the patients.

1) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):

2) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).

3) The diagrams should be completed in Dia - a freely downloadable program from the internet.

## Platform

Windows (all os's)

unix - dumb terminals

The diagram(s) should be made in a progarm called Dia which is freely available on the internet

PHP

Projekt ID: #2931299

Om projektet

Remote projekt Aktiv Apr 30, 2007