HIM FPX 2670 guide: strategic information systems workload

HIM FPX 2670 at a glance: need, choice, governance

The course follows a system decision from start to oversight. The needs assessment identifies what an organization requires from an information system and why. The system selection analysis compares options against those needs. The implementation and governance plan explains how the chosen system will be introduced and managed over time.

Pick a realistic scenario and keep it throughout: a release-of-information system for a hospital HIM department, a clinical documentation improvement tool, an encoder and computer-assisted coding system or a patient portal.

Plan 30 to 40 hours, with the selection analysis taking the most structured work.

HIM FPX 2670 Assessment 1: the needs assessment

The needs assessment asks what the organization needs and why. Gather input from users, such as coders, release-of-information staff, physicians and compliance officers; review current problems, such as backlogs, errors or audit findings; and consider strategic goals and regulations.

Turn findings into prioritized requirements, separating functional needs, such as automated request tracking, from non-functional needs, such as security, availability and a working link to the EHR.

Points slip when needs are vague or describe a particular product. State needs independently, so they can be used to judge any system.

HIM FPX 2670 Assessment 2: the system selection analysis

The selection paper sets two or three candidate systems against your requirements. Use a weighted scoring matrix: assign each requirement a weight based on priority, score each option and calculate totals.

Add total cost of ownership, including licenses, implementation, interfaces, training, maintenance and staff time, over several years. Consider vendor stability, support quality and references from similar organizations.

Recommend an option and explain the reasoning, including where scores were close and what risks remain. Faculty reward transparent methods over confident conclusions.

HIM FPX 2670 Assessment 3: implementation and governance plan

The final assessment plans implementation and ongoing governance. Implementation covers the project team, timeline, data migration, testing, training, go-live support and communication. Governance covers who makes decisions about the system after launch, how changes are requested and approved, how data quality is monitored and how security and compliance are maintained.

Propose a governance structure, such as a steering committee with HIM, clinical, IT and compliance members, and describe its responsibilities and meeting schedule.

Include measures of success, such as turnaround times, error rates and user satisfaction, with baselines and targets.

HIM FPX 2670 information governance

Information governance sits at the heart of health information management, and AHIMA publishes a set of principles for it that covers who is answerable for information, how open the processes are, how data stay accurate and safe, how long they are kept and how they are finally disposed of.

Use those principles as the skeleton of your governance plan. For each one, say how it applies to the chosen system, such as naming a data owner for each module or setting automatic purge rules for records past their retention date.

A principled structure shows faculty the strategic view the course is meant to build, and it gives your committee a clear agenda for its first year.

HIM FPX 2670 strategic alignment

The course title emphasizes strategy. A system decision should support the organization's goals, such as improving revenue integrity, meeting interoperability requirements or reducing compliance risk.

In each assessment, connect the system to strategy. Explain how the needs relate to organizational priorities, how the selected option advances them and how governance keeps the system aligned as priorities change.

Faculty reward papers that see information systems as strategic assets rather than technical purchases.

Name the strategic goal each requirement serves.

Keep that link visible.

Where HIM FPX 2670 papers lose points

Common weaknesses include needs assessments without stakeholder input, selection analyses without weights or costs, implementation plans without training or testing and governance plans that describe committees without decision rights.

Another frequent gap is ignoring data migration. Moving years of records into a new system is risky and costly, and faculty expect it to be addressed.

Measures of success are often missing as well. Without them, there is no way to judge whether the investment paid off.

Overreliance on vendor claims is another weak point.

Sources for HIM FPX 2670

Useful sources include AHIMA practice briefs and information governance resources, HIMSS guidance on system selection and implementation and ONC resources on certified health IT and interoperability.

Peer-reviewed journals in health information management and informatics report on system implementations and outcomes. Analyst reports, such as KLAS research, provide comparative information on vendors, though their methods should be noted.

Vendor materials can describe features but should not be treated as evidence of performance.

Note the date of every comparison you cite.

Prefer recent reviews.

Pacing HIM FPX 2670

The needs assessment sets the pace for everything else, so give it real time. FlexPath students who spend the first ten days interviewing users and listing problems usually find the scoring matrix almost builds itself in the next fortnight, leaving the final week or so for the implementation and governance plan.

GuidedPath fixes the due dates, which makes early user conversations even more important; a few short chats with coders or release-of-information staff in week one can supply evidence for all three papers.

Treat the requirements list and the scoring matrix as living files. Update them as you learn, and carry the final versions straight into the governance plan.

Getting help with HIM FPX 2670

For students balancing work and study, a writer with health information systems experience can draft the needs assessment, the selection analysis and the implementation and governance plan for you to review and submit.

If you work in an HIM department, share the problems you see with current systems in general terms. Real needs make the analysis more convincing, and you make the final choices.

Help can also be limited to the selection analysis, which has the most structure, while you write the needs assessment and governance plan yourself.

Change management in HIM FPX 2670

New systems change people's daily work, and resistance is normal. Coders may worry about productivity during the learning curve; release-of-information staff may fear new errors; physicians may resent extra clicks.

In the implementation plan, address change directly. Involve users in testing, appoint super-users in each area, communicate the reasons for the change and the timeline and plan extra support in the first weeks.

Name a change model, such as Kotter's steps or ADKAR, and show how its stages fit your plan. Faculty reward implementation plans that treat people as carefully as technology.