an electronic health care data system for an urgent care facility* for a (mythical) UMUC Student Health Service clinic

Home Blog an electronic health care data system for an urgent care facility* for a (mythical) UMUC Student Health Service clinic

an electronic health care data system for an urgent care facility* for a (mythical) UMUC Student Health Service clinic

Draft Due Sunday, April 20, 2014 (2359 hours Eastern Time)

Final Due Sunday, April 27, 2014 (2359 hours Eastern Time)

You will use the information learned throughout the course to identify and document a full information system for a small company.  You will apply the basic steps of the SDLC to building the IT infrastructure for an electronic health care data system for an urgent care facility* for a (mythical) UMUC Student Health Service clinic by addressing what actions are taken and what decisions are made in each phase.

Make sure to address key technical issues from this course and to include and specify key elements and components of a computer system as covered in this course, including (but not limited to) the following (in no particular order):

  • CPU type, speed, etc
  • Memory type, size, speed, etc
  • Needed I/O devices
  • Networking
  • Operating system
  • Other required software
  • Shared resources
  • Data format
  • Storage
  • Common file format
  • Databases and DBMS
  • Security*
  • Privacy*
  • Etc.

    …….

The paper should make clear how the functional requirements of the clinic result in the specific technical design specifications, above.

The body of the paper should be no more than 12 point type, not less than 4 pages or 1200 words and not more than 10 pages or 2400 words, not including title page, table of contents, executive summary, and reference bibliography.  The paper will require a title page, a hot-clickable MS Word generated table of contents, executive summary, 4-10 pages of content with incorporation of a minimum of 3 external resources from credible sources, and a Works Cited/Reference page.

The paper should either detail each step in the SDLC (Systems Development Life Cycle) or should detail each step in the The Formal Systems Approach, whichever you determine fits your paper and approach better.  Either way, there should be an emphasis on the technology outcome and how it flows from the functional requirements.

Refer to both the document “SDLC Module 2 from IFSM 201” and other SDLC material in Course Content, and the material on the “The Formal Systems Approach” in Course Content and the Webliography or athttp://polaris.umuc.edu/~kschank/Formal-Systems-Approach.htm.

(Remember that there are many variants of the SDLC other than what is presented in the above module.  You may use any variant of the SDLC that you wish provided that (a) it is logical and complete (and not pulled out of the air), (b) it is appropriate for the system you are designing in your paper, (c) you identify which variant you are using, and (d) you explain it.)

Make sure your paper identifies which approach you will employ, but clearly articulate the steps used to:

  1. Complete a preliminary investigation,      requirements analysis, and system recommendation
  2. Specify a detailed design based on your set      of requirements.
  3. Develop the system according to your design      specification.
  4. Outline how you would test the system and      gain user acceptance.

In your submission, be sure to include any references used in APA style (see the tutorial in the COURSE CONTENT menu) for your source information in a bibliography as well as cite them within the body of your paper.  Be sure to check your work for spelling and grammatical errors before submission.  Yes, spelling and grammar count. The intent of these topics is to provide you with an opportunity to hone your writing skills.

The paper must be your original work, in your own words, and written for this class.  Do not simply copy/paste information from the Web or textbook.  Such submissions will not be accepted for credit.  Research projects should be original work for IFSM 310; therefore, you may not re-use of a paper written you’ve written for a different class.

All “General Paper and Writing Requirements” for all papers (above) must be adhered to for this assignment, except as specifically noted (e.g., table of contents is required, page limits are 4-10 pages, etc.).

 

 

 

 

————–

* (Note that since this is a medical facility, your design should comply with Congressional regulations. Since 1996, the Health Insurance Portability and Accountability Act (HIPAA) details patient privacy and regulations for health care-related businesses.  In addition to HIPAA, there were two acts passed by Congress in 2009 that specifically garnered support for migrating to electronic medical records (EMRs).  The Health Information Technology for Economic and Clinical Health (HITECH) Act is specifically geared at providing financial incentives to health care organizations that migrate towards EMRs, with the intention of eventually replacing the incentives with penalties if providers do not institute electronic record keeping.  The second is the American Reinvestment and Recovery Act (ARRA), which institutes funding for comparative effectiveness research (CER).  Analysis and aggregation of anonymized patient data in regards to conditions, treatment and progress can provide an invaluable source of CER to physicians and healthcare organizations in the treatment of patients.

Therefore, privacy and security requirements should be addressed.  However, computer architecture and system design are the primary subjects of this course and will be more important in the grading than the nuances of Federal law, privacy, and security.  It would therefore be a mistake to take so much time researching and designing for health care privacy and security laws that your hardware and software infrastructure suffered as a consequence.)

You may want to incorporate tables of technical specs, as that is often a more effective way than narrative paragraphs for presenting them.  Also, if you can, please try to draw a diagram of the system, either of its internal architecture and/or of its external connectivity, as appropriate.

 

Submission and Grading

 

…….

Draft Paper

The Draft is due Sunday,April 20, 2014 (Week 5)

The requirements for the draft paper are the same as for the final paper, with the following exceptions.  For the draft:

  • The table of contents and executive summary are optional. 
  • The reference page is required for both draft and final.
  • The page and word count limits are relaxed for the draft.  Just keep it fairly reasonable — not trivially short and especially not too long. (For the final paper, the page and word count limit will be as specified above.)
  • There is no requirement for TurnItIn for the draft paper.  (The Final Paper, of course, must be run through TurnItIn and the originality report must be attached to your submission.)
  • As the intent of the draft is to ensure that you are on the right track and to offer advice on improving the paper before final submission, the grading for the draft paper will be more lenient than the grading for the final paper. 
  • The grading elements, however, will be essentially the same.

 

 

The final paper is due Sunday, April 27, 2014

Submit both the draft and final papers into your Assignments Folder.

This paper earns 18% of the final course grade.  The weight toward the course grade will be 3% for the draft and 15% for the final plan.

Remember that in accordance with the policy in the Syllabus, students must submit all final papers (including this FinDesn) to http://turnitin.com/ and must attach the TurnItIn “Originality Report” to the submission in the Assignments Folder along with the paper itself.  Draft papers and topic selection (DraftPlan) need not be run through TurnItIn.  See “TurnItIn Requirement” in “General Paper and Writing Requirements” for ClassID and password.

Remember that the correct TurnItIn report to submit is the Originality Report, not the Digital Receipt.

 

Grading rubric — 15 points toward course grade for final paper; 5 points for draft

Format, structure, style, and mechanics:   approx. ?30%

Content and substance:                          approx. ?70%

 

…….

Detailed elements of grading rubric:

 

* Format, structure, style, and mechanics (~?30%) ?30%
Title page;

Font and Spacing;

Page length and word count;

Table of contents;

Executive summary;

APA In-text citations;

APA Reference List (bibliography);

Organization and style;

Grammar, correctness, spelling;

Etc.

* Process and Approach (~15%) ?15%
Concept Investigation, Planning, Requirements Analysis, Problem Statement;

Business Requirements / Need Connection;

Facts, Assumptions, Constraints;

Systems Analysis, Problem Investigation;

Analysis of Alternatives;

Systems Design;

Construction, Development, Building, Programming;

Verification and Testing;

Etc.

* HW-SW Design Components (~55%) ?55%
Processor / CPU (w/ specs),

Incl. cache, bus, graphics processor / card, etc.

?6%
Primary Memory / RAM (w/ specs) ?3%
Storage,

incl. Secondary storage / disk (with specs); Tertiary / removable storage / backup storage; virtual memory; etc.

?4%
Networking,

Incl. Network Interface (NIC or Wireless card);

LAN/router;

Broadband modem & ISP / Internet connection; System Networking HW (Routers, Gateways, etc);

Network topology;

Network protocols;

Etc.

?9%
I/O and peripherals ?6%
Operating System,

Incl. OS Type and Characteristics;

File Management;

Utilities;

Etc.

?8%
Application Software ?2%
Security,

Incl. Software (A-V, firewall, etc);

Other security considerations;

Privacy considerations;

Etc.

?7%
Other,

Incl. Business usage;

Databases and DBMS;

Other Shared Resources;

Data format;

Evidence of Requirements & analysis leading to specified design;

Etc.

?9%

…….

 

Score

Each of the above elements will earn …

 

Criteria

90-100% of the maximum possible for the element, when … All required elements are present. Content is complete, and demonstrate mastery of concepts, skills, etc.  Performance and results above and beyond standards and requirements.
80-89% of the maximum possible for the element, when … All required elements are present. Content demonstrates competence in concepts, skills, etc.  Content is substantially complete. Performance and results generally exceed most standards and requirements
70-79% of the maximum possible for the element, when … Major required elements are present. Content is substantially complete and demonstrates understanding of concepts, ability in required skills, etc., with few exceptions and minor incompleteness. Performance and results meet standards and requirements
60-69% of the maximum possible for the element, when … Major required elements are missing. Content is incomplete, or incorrect or demonstrates lack of understanding of concepts, lack of ability in required skills, etc. Performance and results do not meet standards and requirements

(No answer or response at all earns zero points, as does a response with evidence of plagiarism.)

 

…….

…….

Add comment

Academic Research Pro