The physician-clerical-support staffing fee supports physicians' work-style reform from the reimbursement side by having support staff handle clerical work so physicians can focus on care itself. For small hospitals too, it is a highly important fee for both securing physicians and easing their burden.
This article organizes the fee's positioning, then covers ICT-related trends drawing attention in the 2026 revision, workload reduction via voice input and generative AI, staffing and records. Because requirements and points change with revisions, always confirm specifics in the latest primary sources.
Understanding the positioning of the clerical-support staffing fee
This fee evaluates a structure that places a certain number of clerical-support staff to handle physicians' clerical work on their behalf. Tiers are set by the generosity of staffing, so the level a hospital can claim varies with its structure. Correctly grasping your applicable tier is the starting point.
Crucially, the scope of tasks support staff may perform is defined. Assisting with certificates and documents, proxy entry of records, and data organization are covered, while nursing or care-assist acts are out of scope. Misdrawing the line can call the structure itself into question.
Furthermore, requirements on work location and content are set, so merely hiring people does not qualify. A structure where work is done under physician direction and required training are also premises for evaluation. Checking which requirements you meet and how, one by one, is important.
- The claimable level varies by tier based on staffing numbers.
- The scope of tasks support staff may perform is clearly defined.
- Acts amounting to nursing or care assistance are out of scope.
The actual work of clerical-support staff
In practice, support staff handle a wide range: assisting with documents like certificates and referrals, proxy entry into the EHR, order support for tests and bookings, and inputting and organizing data. How much clerical work physicians need not do is offloaded shapes the felt reduction in burden.
At the same time, proxy entry presumes final physician confirmation and approval. Operations that trace who entered and who confirmed and approved on the record are the base supporting the fee's structure. Proxy entry with unclear responsibility tends to become a problem in later audits.
- Document assistance, proxy entry, order support, and data organization are central.
- Proxy entry presumes final physician confirmation and approval.
- Ensure the entrant and the confirmer and approver are traceable on the record.
ICT-use trends drawing attention in the 2026 revision
In recent revision debates, how to evaluate staffing and work when ICT such as voice input and generative AI is used has come up as an issue. As per-person productivity rises with ICT, how to reconsider the thinking on staffing requirements has become a focus.
However, these are only at the stage of debate and trends; how requirements finally land is not fixed. Including whether any easing of staffing requirements materializes, take care that this is not confirmed information, and always check the latest revision content in primary sources such as the health ministry.
- How to evaluate ICT use and staffing thinking is under discussion.
- Trends on easing staffing requirements are under debate, not confirmed.
- Always confirm the final revision content in primary sources.
Reducing staff workload with voice input and generative AI
ICT has practical merit beyond meeting requirements: it lowers the support staff's own workload. Voice input turns dictation directly into text, easing keyboard entry. Generative AI shows its strength in prep work such as drafting standard documents and summarizing long records.
However, the premise that a human always checks AI drafts must not break. Especially for care-related documents, building a two-step check by staff and physician, mindful that inaccurate statements may slip in, is the key to balancing efficiency and safety.
- Reduce keyboard-entry burden with voice input.
- Use generative AI to draft standard documents and summarize records.
- Always check AI drafts in two steps by staff and physician.
Points on claim requirements and building the structure
To claim the fee, in addition to placing the required number of support staff, you must build an operational structure with a clear task scope. Documenting a task-allocation table, clarifying a responsible person, and drawing the line against out-of-scope tasks provide evidence that the structure exists.
Also, training and education for support staff are an important part of the structure. When introducing ICT, including not only tool usage but also confirmation and approval rules and information handling in training balances efficiency with proper operation. Confirm requirement details in primary sources.
- Document the task-allocation table, responsible person, and out-of-scope line.
- Conduct staff training and education as part of the structure.
- Always confirm claim-requirement details in the latest primary sources.
Preparing records and operating proxy entry
In operating the fee, how proxy-entry records are prepared is most scrutinized. A mechanism that records on the EHR who did the proxy entry and when the physician confirmed and approved objectively shows the structure's propriety. Clear distinction between pre- and post-approval records also matters.
When the EHR has proxy-entry and approval-flow functions as standard, such records remain naturally. Sakigake Prime for small hospitals is also designed so daily records live as evidence of the structure. A mechanism uniting operation and records also brings reassurance for audits.
- Have a mechanism that records the proxy entrant and the physician's approval.
- Clearly distinguish pre- and post-approval records.
- Choose an EHR with standard proxy-entry and approval-flow functions.
Common misconceptions in ICT adoption and how to avoid them
Jumping to think ICT lets you cut support staff is dangerous. Revision trends are unfixed, and how staffing requirements will land remains unclear. Rather than building staffing plans solely on ICT adoption, it is wise to leave room to revise once confirmed information appears.
The misconception that AI output needs no checking is also forbidden. Because generative AI output may contain errors, skipping human checks becomes a medical-safety risk. ICT is a tool supporting people, and not breaking the principle that responsibility rests with people is important.
- Do not fix staffing plans solely on ICT adoption.
- Do not skip human checks even for AI output.
- Keep the principle that responsibility rests with people.
Not losing sight of the true goal: easing physician burden
The fee is a means; the goal is an environment where physicians can focus on care. Focusing only on meeting requirements can invert priorities—placing staff yet physicians feel no reduced burden. Design the structure starting from what consumes physicians' time.
The content of the burden differs by physician. Some spend time on documents, others feel weak at data entry. Specifying whose what to reduce and appropriately combining support staff and ICT is the shortcut to making the fee effective.
- Design starting from what consumes physicians' time.
- Specify the content of the burden per physician.
- Combine support staff and ICT appropriately to raise effectiveness.
Anticipated Q&A: the fee and ICT use
Q. Can documents made by generative AI be treated as proxy entry? A. In practice, a flow where AI drafts, staff refine, and the physician confirms and approves is realistic. But organize responsibility on the record and consistency with requirements against primary sources and your rules.
Q. Will staffing requirements really ease in the 2026 revision? A. It is at the stage of debate and trends, not fixed. Avoid firming plans on the premise of easing; once the revision is announced, promptly confirm it in primary sources and be ready to revise the structure.
- An AI-draft, staff-refine, physician-approve flow is practical.
- Staffing-requirement easing is unfixed; do not build plans on it.
- After announcement, promptly confirm in primary sources and revise the structure.
Challenges in recruiting, developing, and retaining support staff
In supporting the fee structure, the most realistic challenge is in fact recruiting and retaining support staff. Securing talent is itself hard for small hospitals, and when a trained staffer leaves, it directly affects the structure and the claim level. Both ease of hiring and of staying are at stake.
For retention, standardized work and an education system help. Rather than learning person-by-person, when procedures and templates are in place and ICT reduces routine work, newcomers ramp up faster and their burden lightens. Ease of work directly leads to structural stability.
Positioning ICT as a burden-reducing tool also makes the role attractive to staff. When voice input and generative AI free them from monotonous entry so they can spend time on higher-value coordination, job fulfillment rises and turnover can be curbed.
- Consider the structure from both ease of hiring and ease of staying.
- Speed up newcomers with procedures, templates, and ICT.
- An environment where ICT lets staff spend time on higher-value work fosters fulfillment and retention.
How to view cost-effectiveness
It is tempting to simply compare fee income against staff labor and ICT costs, but essential effects also lie in parts hard to quantify. Reduced physician burden, leading to securing physicians and preventing turnover, can hold value beyond the fee income over the long term.
When evaluating ICT investment, it is important to capture not only upfront cost but indirect effects such as productivity per staffer and reassurance in record quality and audits. Ignoring effects that are hard to quantify risks misjudging the investment.
- Do not stop at a simple comparison of fee income versus labor and ICT cost.
- Include hard-to-quantify effects like securing physicians and preventing turnover.
- Also consider indirect effects like record quality and audit reassurance.
Checklist for the fee and ICT use
Use the following checklist to inspect your fee structure and ICT-use readiness. Because requirements can change with revisions, use it on the premise that the items themselves are updated against primary sources over time. Start with items you can arrange without strain.
- Do you correctly grasp your applicable tier and claim level?
- Are the staff's scope and the out-of-scope line documented?
- Is there a mechanism recording proxy entry and physician approval?
- Do operations have humans check voice-input and AI output?
- Is training and education for staff conducted continuously?
- Do you follow revision trends in primary sources and revise the structure?
A concrete example of introducing ICT: try small, then expand
Rather than rolling ICT out to every department at once, starting with a trial targeting a few departments or physicians keeps failures small. For instance, trying voice input in a document-heavy department and working with support staff to identify where entry time shortened and what misconversions tend to occur surfaces improvement points grounded in the field's own experience. Picking up not only numbers but users' sense of it is the key to taking root.
Reflect the insights from the trial into templates for standard documents and confirmation procedures, firming up the pattern before expanding to the next department. When drafting with generative AI too, organizing as operational rules which documents make drafts easy to use and where humans must always rewrite spares you from starting over at each rollout and speeds newcomers' ramp-up. Having a pattern also limits quality variance.
In addition, confirming at the trial stage how patient information in voice data and documents is handled, and information management when using external services, is essential. Because how ICT use relates to fee requirements and facility standards can change with revisions, proceed without asserting conclusions and always confirm eligibility and operational details in the latest primary sources such as the health ministry. Balancing safety and propriety builds a structure usable for the long term.
- Trial with a few departments or physicians before expanding.
- Reflect trial insights into templates and procedures to firm up the pattern.
- Confirm patient-information handling and information management at the trial stage.
- Since the relation to requirements changes with revisions, confirm the latest in primary sources.
Summary: rules from primary sources, burden reduction from the field
The clerical-support staffing fee and ICT use are two wheels toward the shared goal of easing physician burden. As debate on ICT advances in the 2026 revision, separating confirmed information from trends and always confirming details in primary sources is essential.
Meanwhile, the fee is only a means. Starting from what consumes physicians' time, combine support staff and ICT appropriately to achieve effective burden reduction. Choosing an EHR where records remain naturally as evidence of the structure is the foundation supporting this effort.
RELATED ARTICLES