NU671 Unit 2 assigning a CPT E&M code for a new patient

The prompt offers you a choice and then loads one option with far more work, which tells you which one it wants. You may assign the code by anticipated time or by medical decision making, but if you choose MDM you must report the level of history taking with its elements, the type of exam with the number of systems and bulleted points, and the level of complexity broken into diagnoses and management options, amount and complexity of data reviewed, and level of risk. That is a detailed piece of documentation analysis and it is the route that demonstrates the skill. Choosing time is legitimate and you should say why if you do, but a post that takes time because MDM looked hard will have less to show. Either way, state the approach explicitly at the top so the reader knows which set of rules to check your work against.

New patient is a status with a definition, and the prompt goes out of its way to say the patient is new for the purposes of the assignment. A new patient is one who has not received a professional service from the physician or another qualified provider of the exact same specialty and subspecialty in the same group practice within the previous three years. It matters because new patient codes carry higher relative values than established patient codes at every level, reflecting the additional work of a first encounter. Saying this in a sentence shows you know that the code family precedes the code level, which is the first branch in the decision and the one most easily assumed rather than reasoned. Getting the family wrong makes every subsequent step irrelevant, however carefully the level is reasoned. It is also one of the few facts the note alone cannot tell you.

The three elements of medical decision making are the heart of the MDM route and they are frequently conflated. The first is the number and complexity of problems addressed at the encounter, which turns on whether problems are self-limited, stable chronic, chronic with exacerbation, undiagnosed and new with uncertain prognosis, or acute and threatening. The second is the amount and complexity of data reviewed, counting unique tests ordered or reviewed, review of external notes, independent interpretation of a test performed by someone else, and discussion with another provider. The third is the risk of complications, morbidity or mortality from the management chosen, where prescription drug management sits at moderate risk and where decisions about hospitalisation or surgery sit higher. Two of the three must be met or exceeded to reach a level, and stating that rule explicitly is a small thing that separates a confident answer.

The history and exam requirements in the prompt are worth handling carefully, because the framework changed. Under the current guidelines history and examination no longer determine the level of an office or outpatient evaluation and management code; they need only be medically appropriate, and the level is set by MDM or by total time. The prompt asks you to identify the history elements present and to count exam systems and bulleted points, which is the older framework's vocabulary. The right move is to do what the assignment asks and to note briefly that these components are no longer level-determining for office visits. That is not contradicting the instruction, it is completing it, and it demonstrates awareness that this area has moved rather than a memorised rule. Doing it that way also protects you from the awkward position of scoring the note against a framework the payer retired, which is the error most likely to appear across the whole thread at once.

If you take the time route, be precise about what counts. Total time on the date of the encounter includes preparing by reviewing records, obtaining and reviewing history, performing the examination, counselling, ordering, documenting in the record, communicating results, and care coordination not separately reported. It does not include time spent by clinical staff, and it does not include time on a different day. Since the prompt asks you to anticipate the time a provider would spend, state your estimate and show the arithmetic against the code's time threshold rather than asserting a level. An estimate with its reasoning visible is defensible; a bare number is not. Time is also the route a marker can check most easily, so an estimate that does not add up will be visible immediately. Show the components you counted and the ones you excluded. Anticipation is only legitimate when it is itemised.

On execution, work from the note itself rather than from an impression of it, and quote or cite the specific documentation supporting each element you claim. That is what the peer prompt is set up for, since classmates are asked to respond to one person who assigned the same code and one who did not, and a disagreement is only useful if both posts show their working. Where the note is ambiguous or incomplete, say so and say what you would have needed, because under-documentation is the real-world problem this exercise is teaching. Support your reasoning with citations as the requirements ask, and end by naming the single element you found hardest to assign, which is the most useful thing you can hand your peers. Name the documentation that would have settled it, and your peers gain something they can use on their own notes.