REFProduct Docs
Data fields
What each field on a Refillops issue means and how to fill it. Examples are illustrative — no real patient or prescription data appears in this doc.
Field reference
| Field | Meaning | Example shape |
|---|---|---|
Patient initials | How a patient is shown on shared queue views — typically first name + last initial. Full name is shown only inside the open issue. Avoid pasting a full name into the initials field. | A. P. |
Rx reference | The pharmacy management system identifier the team uses to look the prescription up. Not the legal dispense record. | Rx #—— or store-specific reference |
Medication display name | A short, human-readable name used in the queue. Use the label the technician will recognise on the shelf. Do not paste payer-rejection text into this field. | Generic strength, dosage form |
Blocker type | Why the prescription is stuck. One of: Claim rejected, Prior auth required, Waiting on prescriber, Inventory delay, Patient action needed, Other. | Claim rejected |
Status | Where the issue is in its lifecycle: Open, In progress, Waiting, Resolved, Reopened. | In progress |
Priority | Time pressure on the work, not interest level. Routine, Soon, or Urgent. | Soon |
Owner | The single team member currently responsible for moving the issue forward. Unassigned items surface at the top of the queue. | One team member |
Next action | A one-line, concrete description of what comes next. Avoid vague text like ‘follow up’. | ‘Call Dr. Patel’s office for new directions’ |
Follow-up due | When the issue should resurface in the queue. Used for PA recheck dates, prescriber callbacks, and patient reminder windows. | A date (and optionally time) |
Review required | Marker that a pharmacist must confirm before the next step is taken — used on AI-assisted suggestions and on alternative path proposals. | Boolean |
Sample chip | Visible label on any issue that came from the optional sample workflow. Sample items are clearly distinguished from real workflow items. | ‘Sample’ chip on the issue card |
Audit history | Append-only list of meaningful changes on an issue — status, owner, priority, accepted suggestion, sent message. | Timeline view on the issue |
What not to put in these fields
- • Full social security numbers, dates of birth, or insurance ID numbers in display fields.
- • Diagnoses or treatment notes that belong in the pharmacy management system, not a workflow queue.
- • Free-text rewrites of payer rejection messages — keep the original wording in the claim case.