CIS8004 Information Systems Planning: Assignment 1 — Mobile HIS Business Systems Planning Document

Information systems consultants tasked with modernizing healthcare technology infrastructure can develop comprehensive business systems planning documents that address mobile device integration with hospital information systems while ensuring security, privacy, and regulatory compliance.

You have been hired as an Information Systems consultant to examine My Health Centre, a fictitious State Government Hospital, with about 20 specialists. My State Hospital offers diabetic services to general public in the state. The services include initial screening, ongoing diagnosis and periodical treatment. The costs are recovered through the State Government subsidy provided.

The Hospital is modern and comes with the state-of-the-art technology infrastructure, including limited wireless systems. The registrar, who is responsible for all patient safety and service quality affairs wanted to revise the IT infrastructure, especially interested in the access to all hospital services available from their existing HIS through mobile devices and tablets inside and beyond the Hospital.

Mobile health applications have transformed from optional conveniences into essential clinical tools. In 2024, over 320 million people worldwide used health apps for symptom tracking, medication management, and nutrition monitoring . Healthcare organizations implementing mobile HIS interfaces report improved workflow efficiency and enhanced patient engagement when security and integration challenges are properly addressed.

Your task is to develop a Business Systems Planning document with full justification as to how these are applicable for the organisation. Your planning document must determine how best to accommodate smart handheld devices to access various services provided by the Hospital through its HIS. Your task is to come with a planning document as to how a smart handheld devices system can be implemented as an effective interface to the HIS in order to improve the business processes. You can include any logical assumptions made with critical analysis however these must be clearly stated.

Healthcare mobile app development costs vary significantly based on complexity and compliance requirements. Simple appointment scheduling apps range from $40,000 to $80,000, while advanced EHR-integrated platforms with AI capabilities can exceed $300,000 . HIPAA compliance alone typically adds 20-50% to baseline development costs due to encryption, authentication, and audit requirements .

You MUST also address the following:

• Any potential customer of My State Hospital can securely access all relevant information pertaining to services offered using a variety of smart handheld devices.
• The planning should involve provision for security, privacy and other end user concerns with using smart handheld devices, along with appropriate justification.
• Your planning document should discuss various technical options available for the new interface (data, integration, application, security, collaboration, network and systems management), along with appropriate justification.
• The planning document should involve consideration for various interfaces (native or SDK) for mobile applications (e.g. Apple App Store, Android Google Store or HTML5 web format).
• The planning document should also include a high level business benefits and budget outlining a provisional list of expense items, along with appropriate justification.
• The planning document should enlist a number of key recommendations for the implementation of the mobile interface to the HIS.
• You don’t have to provide a costing plan now, as this will be done in the second assignment.
• Include a recommendation on how change will be managed and the adoption of the new capabilities will be promoted and monitored.

You will prepare a planning document with an executive summary on how the above aspects can be accommodated. The planning document is a simple report but covering all aspects stated above in a succinct manner. You have been a given a word limit of 1200 words (excluding references, tables and diagrams). You can use any style for business report writing as long as the report is professional and presentable.

Change management strategies prove critical for successful healthcare IT adoption. Research indicates that 27% of employees report their employers rarely or never solicited feedback on pandemic-era technology changes, creating barriers to successful implementation . Effective change management requires visible executive sponsorship, comprehensive training programs, and phased rollout approaches that minimize disruption to clinical workflows.

Submission Requirements

Email submission will NOT be accepted in any circumstance. The assignment should be packaged as one single pdf file and then submitted via the link provided on the course page.

All assessment items are individual submissions. You are asked to submit the assignment simply though the link provided. You are encouraged to discuss the assignment solution path with others to improve your understanding and clarify requirements but you should develop the solution to the assessment items on your own.

All assignment submissions must be completed individually via your study desk. Collusion and cheating is considered to be a very serious issue and all assignments will be closely monitored to ensure that all students are submitting their own work. This ensures that all students are treated fairly and graded on their own knowledge and work. It is acceptable to discuss course content with others to improve your understanding and clarify requirements however you must not discuss the actual assignment solution and the solutions to assignment questions must be done on your own. You must not copy from anyone, including tutors and fellow students, nor provide copies of your work to others. Assignments that do not adhere to this requirement will be deemed as being the result of collusion or cheating.

It is your own responsibility to ensure the integrity of your work. It is recommended that you use passwords to protect your files and ensure that others are unable to access your work.

All assignments must be submitted in electronic form via the link on the Study Desk by the due date. Ensure that you read the extension guidelines as per the USQ/BELA policies and procedures. Only requests that fall within the specified guidelines of USQ/BELA will be considered. Do not assume that all extension requests will be approved.

Marking Criteria

Marks can be deducted for the following errors:

1. Problems with format and structure of report
2. Lack of referencing (Harvard referencing format is the acceptable standard)
3. Spelling, grammar and expression error
4. Indication of plagiarism/collusion
5. Inappropriate use of in-text references
6. Late Submission as per USQ/FBL policies and procedures (This over ride any other information available anywhere in the or course website)

An Assignment submitted more than ten University Business Days after the deadline will have a Mark of zero recorded for that Assignment. The assignments and their due dates are listed in the study schedule to give you some forewarning so that you may organize your study program.

Submission of TURNITIN report NOT required for this assessment item. However, it is student responsibility that the submitted work is plagiarism and collusion free in any circumstances cases related to plagiarism and collision you could be awarded ZERO marks. Students are allowed to use any applications to check their work for plagiarism and collusion. As a general rule, less than 10% is acceptable.

Review of any assessment item is only possible if the request is received within 5 days of the release of the marks of the assessment item. After this, no review request will be accepted.

Your assignment should adhere to the Harvard referencing style. Refer to Chapter 2: Referencing in the Communication skills handbook 3ed by Summers and Smith for guidance on how you should cite your references following this style.

For all assessment item digital file naming convention: When you have an assessment item you need to upload digitally, please use the following naming convention when saving your digital document: (If you do not follow this you will lose marks)

Student last name_Assessment_Name _CISXXXX_Student USQ ID

For example, the first assignment for CIS8004 submitted by Poul Moller, student # 005890420163. If I (Mr. Poul Moller) were uploading this assessment item, file would be named as follow:

Moller_A1_CIS8004_005890420163.doc

Sample Response Content

A student preparing this business systems planning document might structure their analysis around three core pillars: technical architecture, security framework, and change management strategy. For My Health Centre, the mobile HIS interface should prioritize patient portal functionality allowing diabetic patients to access screening schedules, view test results, and receive automated medication reminders through a responsive web application built on HTML5.

The technical architecture recommendation would favor a cross-platform Progressive Web App (PWA) approach rather than separate native iOS and Android development. Cross-platform frameworks like React Native typically reduce development costs by 30-40% compared to dual native builds while maintaining acceptable performance for standard healthcare workflows . The PWA architecture enables offline functionality for rural patients with intermittent connectivity while ensuring seamless updates without app store approval delays.

Security provisions must address HIPAA compliance requirements including end-to-end encryption for data in transit using TLS 1.2 or higher, AES-256 encryption for data at rest, and multi-factor authentication incorporating biometric verification where device capabilities permit . The planning document should mandate Mobile Device Management (MDM) enrollment for all devices accessing PHI, enabling remote wipe capabilities and enforcing security policies such as automatic screen locking after 15 minutes of inactivity.

BYOD policies require particular attention given that 98.3% of hospital physicians currently use personal smartphones during clinical practice, yet only 4.5% receive employer-provided devices . The planning document should establish clear boundaries distinguishing between approved clinical applications and prohibited personal use, with signed employee agreements acknowledging security responsibilities and consequences for policy violations . Containerization technology creating secure encrypted enclaves for hospital data may provide additional protection while preserving user privacy for personal content.

Discussion: Technical Architecture Considerations

Integration architecture for the mobile HIS interface should leverage HL7 FHIR standards to ensure interoperability with existing hospital systems. Research demonstrates that standards-based architectures using Clinical Document Architecture (CDA-2) enable bi-directional data exchange between patient-facing mobile applications and EHR systems while preserving data fidelity and security . The architecture should implement service-oriented design principles allowing independent scaling of components and facilitating future expansion to additional clinical service lines beyond diabetes care.

API gateway patterns provide centralized authentication, rate limiting, and request routing while shielding backend HIS systems from direct mobile client exposure. Microservices architecture separating patient portal functions, appointment scheduling, and secure messaging into discrete services enables independent deployment cycles and reduces risk of system-wide failures. Database design must accommodate both structured clinical data and unstructured patient-generated health data from connected glucose monitors and wearable devices.

Healthcare organizations implementing similar mobile HIS solutions report that induced workload on caregivers during initial deployment phases can impair project sustainability without adequate change management support . Technical implementation success depends equally on human factors including user training, superuser identification, and iterative refinement based on frontline feedback. The planning document should therefore allocate resources not merely for software development but for organizational readiness assessment and post-implementation support structures.

 Change Management and Adoption Strategy

Effective change management for mobile HIS adoption requires visible executive sponsorship, comprehensive stakeholder engagement, and phased implementation approaches. Research consistently identifies active and visible sponsorship as the top contributor to successful change initiatives in healthcare IT, while lack of executive support represents a primary obstacle . The registrar championing this initiative should build a coalition of clinical leaders, IT staff, and administrative representatives to guide implementation decisions and communicate vision throughout the organization.

Phased rollout strategies beginning with pilot divisions before system-wide deployment allow organizations to identify workflow disruptions, refine training materials, and demonstrate quick wins that build momentum for broader adoption . Training programs should combine functional instruction on mobile application features with education on security responsibilities and HIPAA compliance requirements. Peer-to-peer mentoring structures leveraging early adopters as change champions create sustainable support networks that persist beyond initial implementation periods.

Monitoring adoption requires establishing clear key performance indicators including system login frequency, feature utilization rates, and user satisfaction scores. Regular feedback mechanisms through surveys and focus groups enable continuous improvement while celebrating short-term wins maintains organizational momentum . The planning document should specify governance structures for ongoing evaluation and mechanisms for incorporating user feedback into subsequent development iterations, recognizing that successful mobile HIS implementation represents an ongoing journey rather than a discrete project endpoint.

References

1. Dietrich, D., et al. (2024) ‘A Mobile App (Concerto) to Empower Hospitalized Patients in a Swiss University Hospital: Development, Design, and Implementation Report’, JMIR Medical Informatics, 12, e47914. doi: 10.2196/47914. Available at: https://medinform.jmir.org/2024/1/e47914
2. Giordano, A., et al. (2015) ‘A Standards-Based Architecture Proposal for Integrating Patient mHealth Apps to Electronic Health Record Systems’, Journal of Medical Internet Research, 17(9), e210. doi: 10.2196/jmir.4564. Available at: https://pmc.ncbi.nlm.nih.gov/articles/PMC4586338/
3. Prosci (2024) ‘Best Practices for Change Management in Healthcare IT’. Available at: https://www.prosci.com/blog/change-management-healthcare-it
4. The Droids On Roids (2026) ‘Healthcare App Development Cost in 2026’. Available at: https://www.thedroidsonroids.com/blog/healthcare-app-development-cost
5. Uptech Team (2026) ‘Healthcare App Development Cost Breakdown’. Available at: https://www.uptech.team/blog/healthcare-app-development-cost
6. CIS8004 Assignment 1 mobile HIS business systems planning document sample
7. CIS8004 Systems Planning: Mobile HIS Interface Business Report with Security and Change Management
8. Developing mobile hospital information system planning documents
9. What to include in a business systems planning document for healthcare mobile integration

Write a 1,200-word business systems planning document (excluding references, tables and diagrams) for My Health Centre hospital. Address mobile device integration with HIS, security and privacy provisions, technical interface options (native apps vs HTML5), high-level business benefits and budget outline, implementation recommendations, and change management strategies for adoption. Submit as PDF following Harvard referencing style and USQ file naming conventions.

Develop a 3-4 page professional business report analyzing mobile HIS implementation for a state government hospital. Cover secure patient access via smart handheld devices, technical architecture options including cross-platform vs native development, HIPAA compliance security framework, BYOD policy considerations, provisional budget outline, and change management recommendations for successful adoption. Use Harvard referencing format.

Create a business systems planning document for mobile hospital information system integration. Address security, privacy, technical options, budget considerations, and change management for My Health Centre diabetic services.

~~~~~~~

CIS8004 Assignment 2: Cost-Benefit Analysis and Implementation Plan

Building upon your business systems planning document from Assignment 1, develop a detailed cost-benefit analysis and implementation plan for the mobile HIS interface at My Health Centre. Your submission must include: (1) a comprehensive costing plan with itemized expenses for development, infrastructure, security compliance, training, and ongoing maintenance; (2) a risk assessment matrix identifying technical, operational, and security risks with mitigation strategies; (3) a detailed project timeline with milestones and resource allocation for the 12-month implementation period; (4) a stakeholder communication plan addressing internal staff, patients, and regulatory bodies; and (5) evaluation metrics and success criteria for measuring post-implementation performance against business objectives. Submit a 2,000-word report (excluding references, tables and diagrams) in PDF format following Harvard referencing style and the specified file naming convention.

The post Healthcare Mobile Information Systems Planning Guide appeared first on EssayBishops.