NR 640B Week 2 Objectives Draft Example

Course	NR 640B Informatics Nurse Specialist Practicum I
Week	2
Paper type	Practicum objectives draft
Length	About 870 words, 5 pages
Format	APA 7 student paper
School	Chamberlain University
Program	MSN, Nursing Informatics
Updated	October 2026

Free sample paper for NR 640B Week 2

Practicum Objectives Draft: Five Rows, Each With the Competency It Answers, Plain Verbs, the Person Who Can Permit It, a Week and the Evidence It Will Leave

Student Name

College of Nursing, Chamberlain University

NR 640B: Informatics Nurse Specialist Practicum I

Instructor Name

Month Day, Year

What this page is doingThe draft puts each objective on one row with its competency, activity, permission, timing and evidence, uses verbs a supervisor recognizes, writes the permission down and spreads the work across the eight weeks.

Practicum Objectives Draft: Five Rows, Each With the Competency It Answers, Plain Verbs, the Person Who Can Permit It, a Week and the Evidence It Will Leave

The Objectives

No.	Competency it answers	Activity	Permission from	Weeks	Evidence afterward
1	Assessment of information needs	Follow one nursing service request from the day it arrives to the day it closes, attending each step that is open to an observer	Nurse informatics specialist, preceptor	2 to 6	Annotated timeline of the request, with dates and decision points, no patient data
2	Leadership and governance	Attend three optimization meetings and one change advisory board meeting; write notes recording each decision and its reason	Chief nursing informatics officer, as chair	3 to 7	Four sets of meeting notes with a decision log, reviewed by the preceptor
3	Implementation and testing	Write and run a test script for one flowsheet change in the test environment	Preceptor and a clinical analyst	4 to 6	Completed test script with results and any defects logged
4	Data and information management	Spend one hour with the reporting analyst on how admission history completion times are extracted, and write a field list	Manager, reporting and analytics	5	Field list and draft query description, no patient data
5	Education	Draft a one-page tip sheet for a change going live during the practicum	Clinical trainer	6 to 7	Tip sheet draft with trainer's comments

What this page is doingPutting the person who can permit each objective in its own column shows the supervisor that nothing asks for a decision outside their control.

Why These Verbs

Every activity uses a verb the specialist uses about their own work: follow, attend, write, run, spend, draft. None says "understand" or "appreciate," which a supervisor cannot watch happen. If the preceptor read the table aloud at a team meeting, each row would describe something a student could reasonably be doing in that department.

Permission, Written Down

The preceptor agreed to rows 1 and 3 on 3 September. The chief nursing informatics officer agreed to row 2 by email on 4 September, on condition that the student does not speak in the meetings unless invited. The reporting manager's agreement for row 4 is pending; if it does not come by week 4, row 4 changes to reading the existing report specification instead. The clinical trainer agreed to row 5 in person on 5 September. Writing these down prevents a row from depending on a conversation that someone might remember differently.

Evidence That Will Exist

Each row ends in something that can be handed to the faculty member and to the preceptor: a timeline, notes, a test script, a field list, a tip sheet. None contains patient information. Test patients in the test environment are fictitious, and the field list describes fields, not values.

Spread Across Eight Weeks

Rows 1 and 2 run across most of the term because requests and meetings move at their own pace. Row 3 depends on a change being ready for testing, which the preceptor expects in week 4. Row 4 sits in week 5, when the reporting analyst has a gap. Row 5 comes late because the tip sheet must follow a decided change. Weeks 1 and 8 are kept for orientation and the summary.

What Is Deliberately Not an Objective

Building anything in production. Proposing a project. Changing any clinical content. Even small changes to clinical systems can have consequences nobody intended (Ash et al., 2004), which is why build belongs to credentialed staff. Each would need a decision nobody at this site can make for a student, and each would cross from observation into practice the student is not credentialed for. The ANA scope and standards describe informatics work as including analysis, design, implementation and evaluation (American Nurses Association, 2022); this term covers the first and parts of the third and fourth, which is realistic for eight weeks.

How the Rows Were Chosen

The five rows match the five things the preceptor spent the most time on in week one: requests, meetings, testing, data questions and education. Choosing objectives from the specialist's actual week, rather than from a list of competencies, makes each row something the department already does.

What this page is doingChoosing objectives from the specialist's real week is what makes each one easy for the department to say yes to.

What the Preceptor Asked to Change

The first draft had a sixth row: shadowing the physician informatics team. The preceptor suggested dropping it, since that team's work is mostly order sets and physician documentation, which would add little to a nursing informatics practicum and would need another permission. The draft is stronger with five rows than six.

What this page is doingRecording a row that was dropped, and why, shows the objectives were negotiated with the site rather than written alone.

Measuring Progress

At the midpoint, week 4 or 5, the preceptor will mark each row as on track, at risk or changed. Any change is written into the table with its date and reason, so that the week 8 summary can compare what was planned with what happened.

Fit With the Wider Literature

Workflow research in informatics warns that changes look different in practice than in design (Unertl et al., 2010). Following a request and testing a change, rows 1 and 3, put the student where that difference shows.

References

American Nurses Association. (2022). Nursing informatics: Scope and standards of practice (3rd ed.). American Nurses Association.

Ash, J. S., Berg, M., & Coiera, E. (2004). Some unintended consequences of information technology in health care: The nature of patient care information system-related errors. Journal of the American Medical Informatics Association, 11(2), 104-112. https://doi.org/10.1197/jamia.M1471

Unertl, K. M., Novak, L. L., Johnson, K. B., & Lorenzi, N. M. (2010). Traversing the many paths of workflow research: Developing a conceptual framework of workflow terminology through a systematic literature review. Journal of the American Medical Informatics Association, 17(3), 265-273. https://doi.org/10.1136/jamia.2010.004333

Reading the NR 640B Week 2 instructions

Write four or five objectives, usually as a table, with one objective per row. Each row should carry the competency it answers, the activity in verbs a supervisor uses about their own work, the person whose permission it needs, a rough range of weeks and the evidence that will exist afterward. Avoid verbs such as understand or appreciate, which nobody can watch happen. Write each permission down with its date and any condition attached. Make sure every activity is something the site can actually authorize for a student, such as attending a meeting or using a training environment, and nothing requires a decision nobody there can make. Spread the rows across the term, and say what you have deliberately left out and why.

How the NR 640B Week 2 example is put together

The sample's table has five rows. Following one nursing request runs from week 2 to week 6 with the preceptor's permission and leaves an annotated timeline. Attending optimization and change advisory meetings needs the chief nursing informatics officer, who agreed on condition that the student stays silent. Testing a flowsheet change needs the preceptor and an analyst and leaves a completed script. A report extraction hour needs the reporting manager, with a fallback if the answer is no. A tip sheet needs the trainer. The draft explains the verb choices, keeps patient data out of all evidence, rules out production build and project proposals, cites the ANA scope and standards and records why a sixth row was dropped.

Where the points sit in the NR 640B Week 2 rubric

The most expensive drafts list objectives that nobody at the site can authorize, such as implementing a new module or changing clinical content, which leaves the student waiting all term. Next are objectives written in verbs nobody can observe, so the supervisor cannot tell when one is met. Many drafts leave out the permission column entirely, and the first refusal arrives in week five. Evidence described as a reflection or an understanding gives the faculty member nothing to check. Rows bunched into the first three weeks ignore how slowly meetings and requests move. Drafts that never mention patient data in their evidence raise questions a practicum coordinator will ask before approving them.

NR 640B Week 2 help from the desk

Many students write objectives straight from a competency list and only discover in week four that their site cannot grant them. We can help you start from what your specialist actually does, choose verbs a supervisor will recognize and build the permission and evidence columns. Planning a fallback for any row that depends on a busy department is part of the same work. The objectives are yours to negotiate with your preceptor, and the final table is your own. Reading the table aloud together, as your preceptor might, is usually the quickest test of whether each row can be granted.

Get a NR 640B Week 2 example written to your instructions

Paste the objectives template your section uses, the competency list it points at, and a line about what your site will realistically let you near. The example comes back built on that, with rows you could take to your supervisor, inside 24-48h and free the first time.

More NR 640B papers and MSN samples

NR 640B Week 2 questions, answered

How many objectives does a draft usually carry?

Three to five is the usual ask, and the example stays inside that band for a reason: each objective has to be arranged with a person at the site and answered with evidence in Week 8. Two is thin, nine is a signal that none were sized. Check what your own section names, since the count is one of the few things it usually states outright.

My site has not agreed to anything yet. Do I still write the draft?

Yes, and the example shows how. Objectives are written as requests rather than as facts, with the role whose agreement is needed named in the row, and a short note under the table flags any that depend on access the writer does not yet have. Faculty read that as planning. Silence about the arrangement reads as an assumption.

What happens if an objective turns out to be impossible?

It gets revised, in writing, and the revision is usually worth marks rather than costing them. The Week 6 narrative is where most sections expect the change to be recorded, with the reason attached. What marks badly is a Week 8 paper answering objectives that were swapped without a word somewhere along the way.

Where can I find a free NR 640B Week 2 sample paper?

This page holds the full practicum objectives table for an informatics specialist practicum, with permissions and evidence for each row.

Why does the NR 640B Week 2 draft include a permission column?

Each objective needs someone at the site to allow it, and writing down who agreed, when and on what condition prevents a row from failing late in the term.