The role that has view access to Individual Medical Readiness (IMR) data and a limited view of soldier profiles in the Commander Portal is the unit commander role (command access). Commander Portal grants commanders read-only visibility into IMR status for soldiers in their assigned command, paired with a restricted profile view that excludes sensitive clinical details not required for readiness decisions.
Mechanism: how readiness visibility is scoped by role
Commander Portal sits on top of the Medical Operational Data System (MODS), the Army's enterprise platform for tracking medical readiness. Within MODS, modules such as MEDPROS hold the underlying IMR composite data. The portal surfaces a permission-filtered subset of that data to leadership accounts based on duty position and command assignment.
Access is governed by role-based access control (RBAC). The system maps each user to a role, and each role carries a permission set. The commander role is provisioned with IMR view rights and a capped profile scope. That cap is enforced at the data layer, not the interface layer, so sensitive fields are never transmitted to the commander session at all.
IMR itself is a composite score. It aggregates immunization currency, periodic health assessment status, dental readiness classification, and medical deployment eligibility. The commander sees the pass/fail status of each component and the overall readiness category. What the commander does not see is the underlying clinical narrative.
Profile access follows the same logic. Commanders view identity, unit assignment, and readiness-affecting flags. Clinical encounter notes, behavioral health records, and detailed diagnoses remain outside the role's scope. This separation reflects both privacy policy and the operational principle of least privilege.
Plain language: the commander sees who is ready, not why. That distinction is the whole architecture.
Quantified context: what "limited" and "read-only" actually mean
IMR is typically expressed across a small set of readiness categories, commonly reported as ready, ready with reservations, or not ready. The commander sees the category and the component-level status drivers, which usually number between four and six tracked elements.
The term "limited view" is not vague in practice. It maps to a field-level allowlist. Identity fields, grade, unit, and readiness flags are permitted. Clinical detail fields are denied. The allowlist is auditable, which means access changes are logged with user identity and timestamp.
Role provisioning follows command assignment. When a commander assumes command, the role is assigned against the unit's authorization document. When command is relinquished, the role is removed. This lifecycle binding is what prevents stale access from persisting.
Read-only means no write operations. The commander cannot modify IMR status, annotate records, or alter profile data. Corrections flow through medical channels, not command channels. This prevents command influence over clinical determinations.
One caveat worth stating plainly: exact field counts and category labels vary by system version and service component. Treat specific numbers as illustrative of scope, not as fixed specifications.
Edge cases that change who sees what
Command assignment boundaries matter. A commander typically sees soldiers in their assigned command, not the entire installation. When a soldier is attached or cross-leveled, visibility can temporarily follow the gaining command, which creates overlap windows during transitions.
Acting commanders and designated representatives introduce a secondary layer. A first sergeant or executive officer may hold a delegated readiness view without full command authority. These delegated roles usually carry narrower scope than the commander role itself.
Administrative and medical personnel occupy different lanes entirely. MEDPROS administrators and medical providers hold roles with broader clinical visibility but different non-clinical limits. The commander role is not a superset or subset of theirs; it is orthogonal.
Geographic and organizational exceptions exist. Reserve and National Guard structures may route visibility through different command hierarchies, and mobilization processing can temporarily re-scope access.
Red flags to watch for: Access persisting after a change of command Delegated accounts with broader scope than intended Shared login credentials among command teams Profile visibility extending into behavioral health fields Manual overrides of readiness flags outside medical channels
Misconceptions worth correcting
The most common misconception is that commanders can see full medical records. They cannot. The role is deliberately scoped to readiness status and identifying data, not clinical content.
A second misconception holds that IMR data is a commander's tool for personnel decisions. IMR is a readiness reporting instrument, and its use is constrained by privacy policy. Commanders act on readiness status, but they do not adjudicate medical fitness.
A third misconception treats "limited profile" as a technical shortcoming. It is a design feature. The limitation exists to protect the soldier and to keep clinical judgment inside the medical chain.
Counterintuitive detail: broader access does not always improve readiness outcomes. Studies of health information access consistently show that role-appropriate scoping reduces both privacy incidents and inappropriate command pressure on clinicians. The limitation is a control, not a gap.
A fourth misconception is that portal visibility equals data ownership. The portal is a view layer. The authoritative record lives in the source system, and the portal refreshes on a schedule rather than in real time.
Comparison: how roles differ in scope
| Role | IMR view | Profile scope | Write access | Typical holder |
|---|---|---|---|---|
| Unit commander | Yes, full IMR category | Limited (identity, unit, readiness flags) | No | Commanding officer |
| Delegated command representative | Partial IMR | Narrower than commander | No | First sergeant, XO |
| MEDPROS administrator | Yes, full IMR and component detail | Broad administrative fields | Yes, administrative | Readiness NCO |
| Medical provider | Yes, clinical detail | Full clinical record | Yes, clinical | Clinic staff |
| Soldier (self-service) | Own IMR only | Own profile | Limited self-update | Individual soldier |
| Installation safety or HR staff | Aggregate only | None | No | Support functions |
The table shows why the commander role is distinctive: it combines full IMR category visibility with a deliberately capped profile view, and it carries no write authority. That combination is the answer to the access question.
Timeline: how access is provisioned and removed
| Stage | What happens | Typical timing |
|---|---|---|
| Command nomination | Role identified against authorization document | Before assumption of command |
| Account provisioning | RBAC role assigned, scope bound to unit | Days before assumption |
| Access verification | Commander confirms IMR view and profile limits | At or near assumption |
| Active command | Read-only visibility maintained, logged | Duration of command |
| Delegation | Representative accounts created with narrower scope | As needed during command |
| Change of command | Role reassigned to incoming commander | Effective date of change |
| Role removal | Outgoing commander's access revoked | Same day as change |
| Audit review | Access logs reviewed for stale or excess rights | Periodic, scheduled |
Timing varies by organization. The principle is consistent: access follows the duty position, not the person.
Practical actions for commanders and administrators
Verify scope before relying on it. Confirm that your account shows IMR category and the expected profile fields, and confirm that clinical detail fields are absent. If clinical data appears, report it immediately.
Audit delegated accounts. List every account with readiness visibility in your unit and confirm each maps to a current authorization. Remove accounts tied to departed personnel.
Reconcile readiness flags through medical channels. When an IMR status looks wrong, route the correction to the clinic or readiness NCO rather than seeking a manual override.
Set a threshold for escalation. If a soldier's readiness category changes and the cause is not visible in your scope, that invisibility is expected. Escalate to medical, not to the portal administrator.
Document access reviews. Keep a record of who holds command and delegated readiness access, with dates. This supports both privacy compliance and continuity during turnover.
Test the transition window. During attachments and changes of command, confirm that visibility follows the gaining command and that the losing command's access drops off.
Limitations and what this article cannot settle
This explainer describes the stable architecture of role-based readiness access, not a specific system build. Field-level allowlists, category labels, and provisioning timelines change with system versions and service component policy. The exact boundary between "limited profile" and clinical record is set by policy documents that this article does not reproduce.
The article cannot tell you the current status of any individual's IMR, nor should it be used to make personnel decisions. It also cannot substitute for your organization's privacy and access-control guidance, which governs in any conflict.
For any decision affecting a soldier's career, health, or deployability, consult your local medical readiness authority and your command's privacy or access-control office. This article is general educational information about how readiness portals scope access by role; it is not a diagnosis, treatment plan, legal opinion, or personnel recommendation, and it does not promise any outcome. If you are facing an immediate safety or health crisis, contact local emergency or crisis services.