The data-submission add-on requires continuous submission of clinical-performance data in a defined format, and applicable wards are gradually spreading in psychiatry too. The difficulty is that submission is not one-off — quality and continuity are tested.
If daily records are not tied to submission data, a burden of re-collecting information before deadlines arises. This article organizes building a pipeline from daily records to submission data and the idea of a cross-system data platform.
Overview and issues of the add-on
This add-on requires format-compliant clinical data submitted by deadline and at a certain accuracy. Gaps or delays affect claims, so a structure linking administration, billing, and IT is essential.
Eligible wards, formats, submission methods, and deadlines are finely set by regulation and may be revised. Always verify the latest requirements, formats, and deadlines against primary sources such as MHLW notifications.
Why submission data is hard to produce
Submission data does not complete in the EHR alone; information scatters across billing and departmental systems like labs and food service. A mismatch in granularity between required items and daily record items also makes creation hard.
Reconciling data on paper or standalone spreadsheets concentrates transcription and checking before submission, skewing load onto one person. Person-dependent work also risks broken continuity when that person transfers.
Steps to produce submission data smoothly
Ideally, rather than re-entering just for submission, map daily records to the submission format and accumulate them. To spread the burden, building the structure along the following flow helps.
- List required format items and map, in a table, where in daily records each is entered
- Increase selection and templated entry so information remains in a submission-usable form
- Fix a pre-submission step to check for gaps and inconsistencies, with owner and procedure
A checklist for building the structure
Stabilizing continuous submission requires checking both the mechanism and operations. Items to confirm before starting are as follows.
- Are owners and backups assigned to the create, check, and submit steps?
- Is there a procedure to update the mapping and entry items when the format is revised?
- Is there an established way to reconcile EHR, billing, and departmental data?
- Are histories kept so past submission data can be reproduced and verified?
Common misconceptions and failures
The misconception that 'submission can be left to IT' is dangerous. The data comes from clinical, nursing, and administrative records, so frontline entry accuracy governs submission quality.
Also, batching work just before submission tends to break down in busy periods. A habit of tidying data little by little daily and monthly levels the pre-deadline load.
Improving the quality of checks
Submission-data accuracy is greatly shaped by the post-creation check. Mechanically surfacing whether counts or totals diverge sharply from the prior month, or required items are blank, compensates for human oversight.
Gaps found in checking should not end at on-the-spot fixes; tracing why they arose back to the entry stage matters. Operations that avoid repeating the same gaps make the pre-submission burden lighter each round.
A design that does not burden the frontline
Demanding new entry from the frontline for submission raises the record burden and can lower accuracy. If daily records serve directly as submission-data material, the frontline just keeps entering as usual.
Whether submission handling can be positioned as an extension of daily records rather than a 'special administrative job' divides a sustainable structure from an unsustainable one.
The lens of a cross-system data platform
Since submission data does not complete in the EHR alone, a platform aggregating information across hospital systems greatly changes creation and checking efficiency. Handling scattered data in one place is the foundation of continuous submission.
Sakigake Platform aims to be a base that aggregates EHR, billing, and departmental data across systems to support creating and checking submission data. A design where daily records flow naturally into submission eases the owner's burden.
Shaping operations you can sustain
Data submission matters only if sustained. Documenting owners and procedures and keeping operations able to track format revisions balances stable claims with level burden. Turning post-submission review into next-time improvement also matters.
Summary
Meeting the data-submission add-on hinges on a pipeline from daily records to submission data. Grasp three things — frontline entry accuracy, cross-system aggregation, and sustainable operations — and the pre-deadline burden falls sharply. As requirements, formats, and deadlines may change, build the structure on the premise of checking primary sources.
RELATED