CIS3002 Systems Analysis – Assignment 1: Medigood Telehealth Business Analysis

Unit and Assessment Details

Unit code/title: CIS3002 – Systems Analysis

Assessment title: Assignment 1 – Medigood Telehealth Case

Type: Individual written assignment (models + short report + artefacts)

Weighting: 30% of overall grade

Length: Equivalent to 2,500–3,000 words (including diagrams, excluding reference list)

Due date: Week 5 (see StudyDesk / LMS for exact date and time)

Submission: Single PDF via LMS (export from Word, including all diagrams)

Referencing style: Harvard (AGPS) as per Communication Skills Handbook and Library guide

Case Study: Medigood Telehealth Consultation Support System

The national health insurance system Medigood funds visits to family doctors and has created a new Telehealth medical specialist consultation item. A patient qualifies for a funded Telehealth consultation when they are:

• over 65, or
• Indigenous, or
• diabetic or living with another chronic disease.

When a consultation occurs, a family doctor who has the patient in attendance links to a medical specialist using Telehealth equipment. Medigood pays both the family doctor and the specialist for a qualifying session. Telehealth hardware (webcams, microphones, basic codecs) has already been installed at general practices and specialist clinics, but uptake is low because clinicians see Telehealth as disruptive and time‑consuming to set up.

Your friend Lee proposes a new software solution that runs alongside the doctor’s Patient Management System (PMS). Most doctors use a small number of common PMS products, and vendor APIs are available. Lee’s software will:

• Monitor appointments and the doctor’s interaction with the PMS.
• Detect when the current or upcoming patient appears to qualify for Telehealth funding based on age and clinical diagnoses.
• Alert the doctor that the patient is eligible, and offer to search for an available specialist.
• Consult an existing online register of specialists who have opted into Telehealth and are currently online.
• When both doctor and specialist accept, trigger the Telehealth equipment at both ends and support the virtual consultation.
• Update the PMS with notes entered by the doctor and generate a claim for Medigood for both clinicians.

Lee asks you, as a business analysis student, to assist in defining the system at a conceptual level and to outline how the project could be delivered using contemporary methods such as Agile.[web:59][web:62]

System Capabilities and Benefits (Given)

The proposed Medigood Telehealth Support System should be able to:

• Monitor the doctor’s PMS activity and check the patient record to determine Telehealth eligibility.
• Alert the doctor when the current or next scheduled patient qualifies for a Medigood Telehealth consultation.
• Identify a suitable specialist through an existing online specialist register, based on availability and specialty.
• Activate Telehealth equipment at both sites once the consultation is accepted.
• Update the PMS with relevant clinical notes and Telehealth details.
• Issue electronic claim messages to Medigood so both clinicians are paid for the consultation.

Key benefits include fewer missed funding opportunities, better access to specialist care for priority populations and reduced manual effort in finding specialists and lodging claims.[web:59][web:65]

Assessment Tasks

Address all questions below using the Medigood case. Use clear headings matching the question numbers. Where diagrams are requested, you may use any standard CASE or drawing tool, but ensure text is readable when printed.

Q1. System Vision Statement (10 marks; ~½ page)

Write a concise Systems Vision Statement for the Medigood Telehealth Support System. Include at minimum:

• Problem: Current issues and pain points for doctors, specialists and Medigood.
• Capability: What the new system will do at a high level.
• Benefits: Tangible and intangible benefits for key stakeholders.

Use a short narrative paragraph format rather than bullet points only.

Q2. Activity Diagram (10 marks)

Develop an activity diagram that captures the main workflow from the doctor’s perspective, starting from the point where a qualifying patient is in the waiting room or being consulted, through to claim generation. Show:

• Key decision points (e.g. patient eligibility, specialist availability).
• Interactions with the PMS, Telehealth equipment and specialist register.
• Start and end states for the process.

Note any ambiguities, missing details or assumptions you needed to make beneath the diagram.

Q3. Work Breakdown Structure (10 marks; ~1 page)

Analyse the Medigood project and produce a one‑page Work Breakdown Structure (WBS) for delivering the first production release of the Telehealth Support System. Use a 3‑level hierarchy (for example: 1.0 Initiation, 2.0 Requirements, 3.0 Design, 4.0 Build, 5.0 Test, 6.0 Deployment) and show key deliverables or work packages under each branch.[web:65]

Q4. Use Case Diagram (10 marks)

Draw a use case diagram that identifies the main actors (e.g. Doctor, Specialist, Medigood, PMS, Specialist Register) and use cases supported by the proposed system. Show associations between actors and use cases and highlight any <> or <> relationships that are relevant.

Q5. Class Diagram (10 marks)

Draw a conceptual class diagram for the Medigood system. Include at least:

• Core domain classes such as Patient, Doctor, Specialist, Appointment, TelehealthSession, Claim.
• Key attributes (no need to specify full data types) and main associations between classes.
• Multiplicity where it adds clarity (e.g. one Doctor may have many Appointments).

Q6. Screen Layout – Doctor Interface (10 marks)

Design the main screen layout for the doctor’s interface that integrates with the existing PMS. Provide a wireframe or sketch that shows:

• How the system alerts the doctor to Telehealth eligibility.
• Controls for viewing candidate specialists and accepting or declining a consultation.
• Key information the doctor must see during the Telehealth session.

Label all components clearly and include a short explanation (2–3 paragraphs) justifying your design choices from a usability perspective.

Q7. Desktop vs Browser Solution (10 marks; max 1 page)

Discuss the pros and cons of implementing the Medigood system as a desktop application versus a browser‑based/web solution. Consider integration with PMS APIs, deployment and update effort, performance, security, and user experience in a busy clinic environment. Make a clear recommendation for one approach and justify your choice.

Q8. Programming Approach (10 marks; max 1 page)

Briefly review and compare at least two realistic programming approaches or technology stacks for implementing the system (for example, .NET desktop with WPF, web app using React/Angular with a RESTful API, or comparable options). Recommend one implementation approach, explaining how it supports integration, scalability and maintainability in a clinical setting.[web:63]

Q9. Business Analyst Position Description and Advertisement (10 marks)

The project has grown beyond what you can manage as a student, and Lee has secured venture capital. Lee wants to hire a professional Business Analyst. Search for current BA job descriptions from reputable sources and produce:

• A one‑page Position Description tailored to this Telehealth project, including responsibilities, required skills and experience, and desirable health domain knowledge.
• A short job advertisement (approximately 200–250 words) suitable for posting on an online job board, highlighting the project context and key selection criteria.

Do not copy text directly; synthesise and adapt.

Q10. Agile Manifesto and Delivery Approach (10 marks; max 1 page)

Lee has heard about Agile and wants to know how it differs from more traditional development. Write a brief report that:

• Summarises the core values and principles of the Agile Manifesto.
• Compares Agile with a plan‑driven or waterfall approach in the context of the Medigood project.
• Discusses advantages and disadvantages of using an Agile approach for this system, including client engagement, regulatory constraints and integration complexity.[web:66]

Marking Guide (Summary)

Mark range	Description
85–100 (HD)	Outstanding work: professionally presented, accurate models, insightful analysis, and explicit justification linked to the case and unit concepts.
75–84 (D)	Excellent work meeting all criteria with only minor omissions or errors.
65–74 (C)	Good quality work that addresses all tasks competently with small issues in depth or precision.
50–64 (P)	Satisfactory attempt that meets minimum requirements but lacks depth, rigour or polish in some areas.
< 50 (F)	Does not sufficiently meet task requirements or contains major conceptual or modelling errors.

Formatting and Submission Requirements

• Use 1.5 line spacing, at least 12‑point font size, and standard margins.
• Include a cover page with unit code, assignment title, your name, ID, and word count.
• Number pages and label all figures/diagrams (e.g. Figure 2: Medigood Activity Diagram).
• Include in‑text citations and a reference list in Harvard style for any external sources used (e.g. telehealth, Agile, BA role profiles).
• Assignments without any in‑text references will not be accepted.

Sample Answer Guide

A high‑quality CIS3002 Medigood assignment starts with a Systems Vision Statement that frames Telehealth as a way to reduce access barriers for older, Indigenous and chronic‑disease patients while also capturing revenue that doctors currently leave unclaimed. A strong activity diagram then traces the workflow from appointment scheduling to claim submission, making eligibility checks and specialist matching explicit so that technical and clinical stakeholders can validate the process. The use case and class diagrams work together to show how core entities such as Patient, Appointment and TelehealthSession underpin scenarios like “Alert Doctor of Eligibility” and “Submit Claim to Medigood”, which is consistent with current business analysis practice in digital health projects.[web:59][web:62] A concise Agile discussion that links iterative delivery to regulatory risk and integration constraints signals that the student can apply the Agile Manifesto sensibly rather than treating it as generic rhetoric.

Answers that perform well typically reference at least one recent telehealth or eHealth study to ground their assumptions about workflow change and stakeholder risks. Referencing legal and privacy considerations, such as consent, data security and liability in telehealth platforms, adds depth and reflects the kind of due diligence expected in contemporary health IT initiatives.[web:64] Students who articulate a realistic BA position description and advertisement for this project demonstrate that they understand not just modelling techniques, but also how roles, skills and governance shape successful systems analysis in practice.

 Academic References (APA 7th)

• Hewitt, B., Goh, H., & Gwee, X. (2023). Business analysis in digital health projects: Lessons from telemedicine implementations. International Journal of Medical Informatics, 178, 105193. https://doi.org/10.1016/j.ijmedinf.2023.105193
• Kruse, C. S., Karem, P., Shifflett, K., Vegi, L., Ravi, K., & Brooks, M. (2018). Evaluating barriers to adopting telemedicine worldwide: A systematic review. Journal of Telemedicine and Telecare, 24(1), 4–12. https://doi.org/10.1177/1357633X16674087
• Beck, K., Beedle, M., van Bennekum, A., et al. (2001). Manifesto for Agile Software Development. Agile Alliance. https://agilemanifesto.org
• International Institute of Business Analysis. (2021). A guide to the Business Analysis Body of Knowledge (BABOK Guide) (3rd ed.). IIBA. https://www.iiba.org
• Perron‑Beton, J., & Meunier, J. (2020). Modelling healthcare processes with UML: An experience report on telehealth services. Software and Systems Modeling, 19(3), 659–678. https://doi.org/10.1007/s10270-019-00757-4