Personas

Who does the workflows we are rolling out, and the RPMS user profile each is set up with. The source is docs/product-cycle/PERSONAS.md and the analyst's profiles in docs/product-cycle/profiles.json.

Persona	Surface today	Profile	Use cases
Registration / front desk `front_desk_clerk`	BPRM, roll-and-scroll (AG)	Patient Registration Technician, Front desk (REGISTRAR/SCHEDULER)	27
Registration supervisor / patient registration manager `registration_supervisor`	BPRM, roll-and-scroll (AG)	Patient Registration Technician	4
Scheduling clerk `scheduler`	BPRM, IHS Windows Scheduling (BSDX), roll-and-scroll (SD)	Schedular	12
Medical assistant `medical_assistant`	VueCentric	Medical Assistant	9
Nurse (RN/LPN) `nurse`	VueCentric; BPRM for ward transfers and the census	RN/LPN/LVN	16
Physician, NP or PA `provider`	VueCentric	Physicians/PA/NP	23
Coder / data entry `coder`	VueCentric, roll-and-scroll (PCC data entry)	none yet	3
Billing technician `billing_technician`	roll-and-scroll (3P Billing, A/R)	none yet	4
Clinical / quality manager `site_manager`	VueCentric Reports tab, roll-and-scroll (PCC reports, BGP)	none yet	4
Care / case manager (nurse case manager, public health nurse) `care_manager`	iCare (BMX; IRIS stacks only)	none yet	9
Medical staff office `credentialing_coordinator`	roll-and-scroll (Kernel user management, Staff Credentials)	none yet	3
Pharmacist `pharmacist`	roll-and-scroll (Outpatient Pharmacy)	none yet	1
Laboratory technician `lab_technician`	roll-and-scroll (Lab)	none yet	1
Purchased/Referred Care clerk `prc_clerk`	roll-and-scroll (CHS/PRC, RCIS)	none yet	3
Admissions / ADT clerk `admissions_clerk`	BPRM, roll-and-scroll (ADT)	none yet	3
Health information (medical records) technician `him_technician`	BPRM, roll-and-scroll (ADT incomplete chart)	none yet	4
Patient benefits coordinator `benefits_coordinator`	BPRM, roll-and-scroll (AG)	none yet	10
Behavioral health provider (psychiatrist, psychologist, social worker, counselor) `bh_provider`	VueCentric; the Behavioral Health System (AMH)	none yet	1
The patient `patient`	the clinic, a printout, the patient portal	none yet	2

Open questions on the profiles

scheduler mini-registration (SDZREGMENU, AGGRPC). The product owner decided on 2026-11-03 that the scheduler registers a caller while booking (S-REG-05, IHS option BSDAM MINI REGISTRATION). The build gives PROFILE,SCHED the key SDZREGMENU, which unlocks it, and AGGRPC, the registration GUI context a client files the patient under, as a secondary menu (rpms-ops#1056). The sheet's scheduler row holds neither. Does a scheduler at this site mini-register, and should the scheduler profile carry SDZREGMENU and AGGRPC?
front desk: one user or two. The sheet has one Front desk (REGISTRAR/SCHEDULER) profile, with keys AGZMENU and SDZMENU and secondary menu BSDXRPC. The build splits the desk: PROFILE,REG holds AGZMENU with secondary menus AGPAT, CIAV VUECENTRIC and AGGRPC, and PROFILE,SCHED holds the scheduling side (rpms-ops SEEDPERS). PROFILE,REG holds neither SDZMENU nor BSDXRPC. Does one person work both at this site, so the desk needs one user with both?
secondary menu MAG WINDOWS (all users) and key MAGDISP CLIN (clinical profiles). MAG WINDOWS is not in OPTION (#19) on YDB stack 0930. Imaging 3.0 is registered, but its source is not in the public release. Drop both on our builds, or is Imaging expected?
CIAV VUECENTRIC. No profile lists it. It is the context VueCentric signs on under, and it is in OPTION (#19) on YDB stack 0930. Does AKMOCORE's menu tree reach it, or should the clinical profiles carry it as a secondary menu?
fileman_access. The sheet says M; the screen in User-Setup.docx shows Md for a physician. Which one per profile?
signature block, provider class. SIGNATURE BLOCK PRINTED NAME is empty on every row; PROVIDER CLASS is empty for the prescriber and the three HIM profiles. Per person rather than per profile?
sheet spellings. or_key on the Medical Assistant row reads ORMAS on the sheet and OREMAS here: no ORMAS is in SECURITY KEY (#19.1) in FOIA or on the pinned build, OREMAS is the stock clerk order key, and PROFILE,MA, as the analyst built that user, holds it. Kept in 'name' as written (Schedular); the title and user class cell 'PHYSICIAN/ PHSICIAN/PHYSICIAN ASSISTANT/NURSE PRACTITIONER' is encoded as three alternatives.
registration supervisor keys. The sheet gives the supervisor the Patient Registration Technician profile plus AGZMGR, AGZHOME, AGZREPORTS and AGZDELHRN. The build files PROFILE,REGSUP with PROFILE,REG's menus and key, plus AGZMGR, AGZVIEWSSN (AG*7.1*17 gates the SSN edit on it) and DGPF ASSIGNMENT (patient record flags), so the clerk's denial scenarios keep a user who is allowed (rpms-ops#1091). AGZHOME, AGZREPORTS and AGZDELHRN are keys on the build (security-keys/), but PROFILE,REGSUP does not hold them. Should the supervisor also hold AGZHOME, AGZREPORTS and AGZDELHRN, and does the sheet's supervisor hold AGZVIEWSSN and DGPF ASSIGNMENT?
billing technician (no row on the sheet). The build ships PROFILE,BILL so the billing scenarios run as a billing user, not the operator: primary menu AKMOCORE (3P Billing and A/R are already on it), service/section BUSINESS OFFICE, title BILLING TECHNICIAN, keys ABMZMENU (3P Billing), ABMDZ EDIT CLAIM AND EXPORT (Edit Claim, where a claim is approved, and the 837 export) and BARZMENU (A/R, payment posting). No person class, and no manager, table maintenance, site setup, cancel-claim or manual-claim key. Is this how a clinic sets up its billing technician? Which person class, if any? Should it also hold ABMDZ ELIGIBILITY EDIT (the 3P Eligibility menu) or ABMDZ PAYMENT POSTING (posting in 3P rather than A/R)? Which keys make the billing supervisor?
which key manages consults (lakeraven-ehr#578). The EHR grants consult management on a SECURITY KEY. Its old name, GMRC MGR, is a menu option, not a key. GMRC101 is a key on the build, but what it governs is unconfirmed. Which key does a user who manages consults hold here, if any?
which key verifies eligibility (lakeraven-ehr#578). The EHR grants eligibility verification (Coverage read and write) on a SECURITY KEY; its old name, APCL VERIFY, is in no package. Keys on the build that may fit: AGZ X12 270/271 PROCESSING, AGZMENU. Which key does the person who verifies eligibility hold?
which keys give dental access (lakeraven-ehr#578). The EHR grants dental access (Procedure read and write) on SECURITY KEYs; its old names (DENTP PROVIDER, DENTP SUPERVISOR) are in no package. Keys on the build that may fit: ADEZMENU, ADEZMSUPFUN. Which keys do a dentist and a dental supervisor hold? Is dental in scope for us?