Import planning guide
This page is documentation only. CSV import is not enabled in this build — when it ships, it will follow the rules described here.
Status
CSV import is not live. Do not assume any UI you see is a working pipeline. This guide exists so pharmacy teams can prepare data before import is available.
What an import would and would not do
- • Import would create prescription issues and linked objects (claims, PA cases, patient updates).
- • Import would not become a system of record for dispensing — that stays in your pharmacy management system.
- • Import would not sync back to insurers, prescribers, or patients.
Accepted fields (planned)
| Field | Required | Notes |
|---|---|---|
patient_initials | Yes | Use first name + last initial; do not include full name. |
rx_reference | Yes | Your pharmacy management system identifier. |
medication_display | Yes | Short shelf-friendly name. |
blocker_type | Yes | One of the documented blocker types. |
priority | No | Defaults to Routine. |
owner_email | No | Must match an existing team member. |
next_action | No | One-line description of next step. |
follow_up_due | No | ISO date. |
notes | No | Free text; appended to the timeline. |
Privacy-safe import tips
- • Only include the smallest amount of patient information needed to identify the issue at the counter.
- • Strip diagnoses, insurance ID numbers, and dates of birth before exporting from your management system.
- • Use a secure transfer method — encrypted email or a signed upload link — not a public file share.
- • Delete the source CSV from local devices after import is confirmed.
No PHI over-collection
Refillops does not need full patient identifiers to run the workflow. If a field is not in the accepted list above, don’t include it. Over-collection expands your team’s compliance surface for no operational benefit.
Import review before saving
When import ships, every batch will go through a review screen — row counts, mapping confirmation, sample rows, and a destructive-action summary — before anything is written. There will be no silent background imports.
Sample workflow vs. real import
The sample workflow loader (Settings → Data) loads clearly-labelled example issues for training. It is unrelated to a real import. Always clear sample data before relying on the queue for live counter work.