A remote outpatient and emergency coder, defined duty by duty with a standard and a data source for each, in an HI305 Unit 2 job description. Searches like "hi 305 unit 2 assignment example", "hi305 unit 2 sample" and "hi305 unit 2 example" land here.
What a finished HI305 Unit 2 job description looks like
Two pages, a three-column table doing most of the work. The header gives the title, Coding Specialist II, outpatient and emergency; the reporting line to the coding supervisor; full-time remote status; and core hours when the coder must be reachable. A two-sentence summary follows. The table pairs each of seven duties with its standard and its source. Coding emergency visits points to the department's productivity standard, currently [ten] records per productive hour, read from the encoder's weekly report. Accuracy carries [95] percent on a quarterly review of [30] records. Physician queries must follow the department's approved template. Holds must carry a note within [two] days, checked against the unbilled list. Hiring requirements come in two lists: a nationally recognized coding credential and [two] years of outpatient coding are required, emergency experience preferred. Remote conditions close the page.
How a HI305 Unit 2 example is structured
The layout matches a typical hospital template, which lets recruitment reuse any block unchanged. Header and summary open it, the summary stating what the role exists to deliver: complete, accurate codes on outpatient and emergency accounts within [48] hours of the visit. The duty table follows, ordered by share of the week, with a note beneath it that the numbers come from the department's written productivity standard and may be revised, so the description points to that standard rather than freezing a figure. Orientation gets a paragraph of its own: for the first [90] days, productivity is measured but not appraised. Requirements come next, then remote working conditions: a private workspace, the organization's own device, no printing, and connection only through the secure access the hospital provides. Signature lines and a revision date close it.
Header for a remote role
Title, reporting line, full-time remote status and the core hours when the coder must answer messages, which matter more for a remote role than a shift start.
Duty, standard, source
Seven duties in a three-column table, each with the measure that will judge it and the report or review that supplies the figure.
A number that can change
Productivity pointed to the department's written standard rather than fixed in the description, so a revised standard does not make the document wrong.
Orientation carved out
Productivity measured but not appraised in the first [90] days, stated in the description so a new coder knows the ramp is expected.
Working from home, securely
Private workspace, organization-issued device, no printing and access only through the hospital's secure connection, written as conditions of the role.
Where marks go in HI305 Unit 2
A duty with no measure attached is the costliest flaw: codes outpatient records accurately, communicates with physicians. Neither sentence tells a supervisor what counts as meeting the job, which is what this unit is usually testing. Hard-coding a productivity number into the description is a quieter error, since the standard will change and the document then contradicts the department. Accuracy described as high, with no percentage, sample size or review cycle, cannot be appraised. Remote roles need their conditions written down; leaving out workspace, device and printing rules costs points in sections that raise privacy. Credentials listed without distinguishing required from preferred shrink the applicant pool for no stated reason. Descriptions that forget the query process ignore the duty where coders most often need a clear rule.
Get a HI305 Unit 2 example written to your instructions
Name the role the Unit 2 prompt hands you, coder, release of information specialist or another, and send the instructions and rubric with any productivity figures the course provides. You receive a description with every duty tied to a measure, in 24-48h, and the first sample is free. Remote or on-site conditions follow the scenario.
HI305 Unit 2 questions, answered
Should the job description include productivity numbers?
It should point to them without freezing them. The example names the department's written productivity standard and quotes the current figure in brackets, noting that the standard governs if the two ever differ. That keeps the description accurate after a revision and still tells a candidate what the job expects. Accuracy and turnaround targets are treated the same way.
Can I name a specific coding credential?
Yes, if the scenario or your department requires one, and many coding job descriptions name the credential they accept. The example says a nationally recognized coding credential so that it fits several employers, and lists outpatient experience beside it. Whatever is named should be defensible as necessary for the work, since an unnecessary requirement narrows the pool without improving it.
What belongs in the remote work section?
The conditions that protect the record when the work leaves the building: a private space where screens cannot be overseen, the organization's device rather than a personal one, no printing or local saving, and access only through the connection the hospital supplies. The example writes these as job conditions, so a breach of them is a performance matter the supervisor can address.