Measuring decision latency in patient intake

Published October 28, 2026

A grounded dispensary operations note for dispensary managers: patient intake with explicit evidence, decision rights, and a verified close.

Question and scope

State the observation window, the sites or teams included, and the exclusions before collecting the first case. The population should include cases handled by every owner and channel in scope, not only the queue with the cleanest records. Record how corrections, reopens, and duplicate requests are treated so inventory variance cannot be inflated by reclassification. State whether the study covers one team, one client, or all cases in the defined service. When a value is missing, record the missing state and the reason instead of leaving an empty field in the extract. The October 28 patient intake exception log should show the reason code, owner, and release decision.

The study measures the record and the handoff, not the professional judgment of pharmacist or the legal outcome of the work. State how duplicate requests are identified and whether they are merged, linked, or counted separately. A case is complete only when the inventory scanner shows the approved destination value and the inventory count sheet supports it. Write the decision the study is meant to inform before choosing the measure. If the evidence is sensitive, record the approved reference and access path rather than copying the content. The October 28 patient intake recovery test should record the restore point and the intake completeness result.

Population and unit

Record the opening count by owner and channel, because a single total can hide a queue concentrated in one person. A denominator that changes during the window should be reported separately for each period. The definition should make it possible to classify a case without asking the person who did the work. If a request was reopened after the window, keep it in the original population and report the later event separately. Record this decision in the study log with the case key, the review date, and the person who approved the classification. The October 28 control note for Dispensary VA should name the patient intake source, the owner, and the next review time.

Include cases opened before the window but closed inside it only when the protocol says they belong to the population. A case that moves between owners stays one case unless the process defines a new requirement at the handoff. Use plain language in the definition and add one example and one non-example for the reviewer. Separate cases opened before the window from cases opened and closed inside it, and report both counts. If the source changes after the observation, preserve the earlier value and add a dated note instead of replacing it. The October 28 evidence trail for patient intake should show the source version and the vendor representative decision.

Definitions and measures

Define how a correction after close is linked to the original case and whether it creates a new case. A blank field, a not-applicable field, and a confirmed negative field should have different codes. Before collection, test the definitions on a missing recall log, a reopened case, and a handoff. Write the start and stop events as observable actions, not as opinions about whether the work felt finished. Use the same note in the case file and the study extract; do not create a second version in a personal document. The patient intake review at Dispensary VA should state whether the recall log was current on October 28.

Name the owner who can declare a case complete, and record that role in the data dictionary. Define allowed values for status, reason, owner, and evidence state before collection. Use the same status vocabulary in the queue, the evidence extract, and the report so a case does not change category. Keep a change log for every definition adjustment and the date it took effect. Keep the measurement note short enough to read with the case and specific enough to support the reported credential expiry count. The October 28 patient intake note should distinguish a missing vendor invoice from a confirmed negative.

Data dictionary and evidence

Each case needs the source, the observation time, the field supported, the owner, and the reviewer. If a field is derived, record the formula and the source fields used to calculate it. Store sensitive evidence in the approved repository and keep only the reference in the analysis file. Pilot the dictionary with two reviewers and compare their classifications before the main sample. Link the observation to the exact field in the prescription queue and to the vendor invoice that supports it. The compliance lead decision on patient intake should be dated October 28 and linked to the vendor invoice.

Test the dictionary on five cases before the full sample; ambiguous fields should be fixed before collection, not after. Version the dictionary and report which version was used for each observation period. Record the source identifier, the field name, the observation time, and the reviewer for every extracted value. Use a separate field for reviewer notes so the coded values stay comparable. If the case moved between owners, include both owner periods in the review note and name the handoff time. The October 28 patient intake close should name the destination field, the approver, and the intake completeness check.

The data dictionary should name the allowed values for status, exception reason, owner, and close evidence. Name the required fields for each article type and mark conditional fields in the dictionary. Use one row per case and one column per required field; do not bury evidence in a long free-text note. Record the source location, not just the file name, so a reviewer can reopen the exact evidence. When a value is missing, record the missing state and the reason instead of leaving an empty field in the extract. The October 28 patient intake exception log should show the reason code, owner, and release decision.

Sampling and collection

Use a random or systematic start rule for the first case, then take consecutive cases within each stratum. Use the same collection form for every case and keep the original record linked to the extracted fields. Include reopened, unresolved, and exception cases in the sample frame. Record the sampling frame as an export with a date, filter, and row count. If the evidence is sensitive, record the approved reference and access path rather than copying the content. The October 28 patient intake recovery test should record the restore point and the recall closure time result.

Use a random or systematic start rule for the first case, then take consecutive cases within each stratum. Use the same collection form for every case and keep the original record linked to the extracted fields. Do not expand the sample only because the early result looks weak or strong. If a selected case is out of scope, replace it only with the next case in the same stratum and record the substitution. Record this decision in the study log with the case key, the review date, and the person who approved the classification. The October 28 control note for Dispensary VA should name the patient intake source, the owner, and the next review time.

A convenience sample of recently closed cases will overrepresent easy work and underrepresent the tail that needs attention. Collect the case from the dispensary management system, the patient intake form, and the approval record, and stop at the verified close. Do not expand the sample only because the early result looks weak or strong. Keep a table of planned, eligible, selected, and reviewed counts for each stratum. If the source changes after the observation, preserve the earlier value and add a dated note instead of replacing it. The October 28 evidence trail for patient intake should show the source version and the compliance lead decision.

Analysis and reporting

Report the eligible count, the sample, the missing-field rate, the exception rate, and the unresolved count at the close of the window. Keep descriptive findings separate from causal claims. Record the sample date, the denominator, the numerator, and the exclusion count for every reported rate. Report the numerator, denominator, observation window, and exclusion count for each measure. Use the same note in the case file and the study extract; do not create a second version in a personal document. The patient intake review at Dispensary VA should state whether the access log was current on October 28.

Keep case-level detail available for review, because a summary chart without records cannot support a decision. Compare periods only after checking the case mix, the definitions, and the queue rules. Write the finding in plain language and separate what was observed from what the team believes caused it. Report the numerator, denominator, observation window, and exclusion count for each measure. Keep the measurement note short enough to read with the case and specific enough to support the reported credential expiry count. The October 28 patient intake note should distinguish a missing patient intake form from a confirmed negative.

Limitations

The study cannot determine whether the professional decision was correct, only whether the record and handoff are reconstructable. A clean summary can hide missing evidence, especially when the operator who did the work is also the reviewer. If the queue changed during the window, explain how the change affects the denominator and the interpretation. If the reviewer performed the work, use a second reviewer for a subsample and report the disagreement. Link the observation to the exact field in the dispensary management system and to the patient intake form that supports it. The dispensary manager decision on patient intake should be dated October 28 and linked to the patient intake form.

Small samples are sensitive to one case; report the instability instead of presenting a percentage as a stable rate. Small samples are unstable; report the range and the cases that create the variation. Record the response or access problems that prevented a case from being reviewed. State what a follow-up study would measure and which population it would include. If the case moved between owners, include both owner periods in the review note and name the handoff time. The October 28 patient intake close should name the destination field, the approver, and the intake completeness check.

Review and next action

If the action affects incomplete intake, route it to compliance lead and record the approval before implementation. Repeat the protocol with the same definitions and window, then compare the same measures. Record the owner, the due date, and the exact change that will be tested at the next review. Keep the prior procedure available so the next reviewer can compare the old and new states. When a value is missing, record the missing state and the reason instead of leaving an empty field in the extract. The October 28 patient intake exception log should show the reason code, owner, and release decision.

Repeat the protocol after the change with the same definitions, window, and exclusions. If the action changes unlogged recall, record the approval from vendor representative before implementation. Set the next sample date before closing the review, so the action does not drift. Schedule the next review before the action begins, not after the result arrives. If the evidence is sensitive, record the approved reference and access path rather than copying the content. The October 28 patient intake recovery test should record the restore point and the cash variance rate result.

Sources

• U.S. Food and Drug Administration - regulatory information
• U.S. Department of Health and Human Services - HIPAA
• Centers for Medicare and Medicaid Services
• United States Pharmacopeia