---
title: "EHR Workarounds: When Healthcare Workflows Don't Fit the EHR"
description: Which healthcare workflows belong in the EHR, and which need a separate coordination layer? A workflow-by-workflow method for intake, referrals, and more.
image: https://blog.kintone.com/hubfs/Blog%20Files/HCS6%20-%20Hero%20-%20Kintone-Style%20Healthcare%20Coordination%20Illustration.png
---

[![Kintone](https://blog.kintone.com/hubfs/KintoneGlobal/svg/logo_kinton_black.svg)](https://www.kintone.com/en-us/)

[![Kintone](https://blog.kintone.com/hubfs/KintoneGlobal/svg/logo_kinton_black.svg)](https://www.kintone.com/en-us/)

![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_search_black.svg)

- Product
  
   Product![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_plus.svg)![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_back.svg) 
  
    - Product ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_plus.svg) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_back.svg) 
      
          - [Intro to Kintone](https://www.kintone.com/en-us/intro/)
          - [Why Kintone](https://www.kintone.com/en-us/why-kintone/)
    - Features ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_plus.svg) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_back.svg) 
      
          - [How Kintone Works](https://www.kintone.com/en-us/how-kintone-works/)
          - [App Template Library](https://www.kintone.com/en-us/features/app-templates/)
          - [Extensions](https://www.kintone.com/en-us/features/extensions/)
          - [Native Kintone Plug-ins](https://www.kintone.com/en-us/features/plugins/)
          - [Kintone AI](https://www.kintone.com/en-us/features/ai/)
          - [System Administration](https://www.kintone.com/en-us/features/administration/)
          - [Security](https://www.kintone.com/en-us/security/)
- Solutions
  
   Solutions![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_plus.svg)![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_back.svg) 
  
    - [Solutions by Department](https://www.kintone.com/en-us/departments/) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_plus.svg) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_back.svg) 
      
          - [Operations](https://www.kintone.com/en-us/departments/business-operations/)
          - [Sales](https://www.kintone.com/en-us/departments/sales/)
          - [Customer Support](https://www.kintone.com/en-us/departments/customer-support/)
          - [HR & Admin](https://www.kintone.com/en-us/departments/hr-admin/)
          - [Marketing](https://www.kintone.com/en-us/departments/marketing/)
          - [Manufacturing & Retail Management](https://www.kintone.com/en-us/departments/manufacturing-retail-management/)
          - [IT Support](https://www.kintone.com/en-us/departments/it-support/)
    - [Solutions by Function](https://www.kintone.com/en-us/functions/) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_plus.svg) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_back.svg) 
      
          - [Convert spreadsheets to databases](https://www.kintone.com/en-us/functions/convert-spreadsheets-to-databases/)
          - [Data Management](https://www.kintone.com/en-us/functions/data-management/)
          - [CRM & Sales Management](https://www.kintone.com/en-us/functions/crm-sales-management/)
          - [Project Management](https://www.kintone.com/en-us/functions/project-management/)
          - [Workflow Management](https://www.kintone.com/en-us/functions/workflow/)
          - [Remote Work](https://www.kintone.com/en-us/functions/remote-work/)
          - [Recruitment & Hiring](https://www.kintone.com/en-us/functions/recruitment-hiring/)
    - [Solutions by Industry](https://www.kintone.com/en-us/industries/) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_plus.svg) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_back.svg) 
      
          - [Manufacturing](https://www.kintone.com/en-us/industries/manufacturing/)
          - [Real Estate](https://www.kintone.com/en-us/industries/real-estate/)
          - [Retail](https://www.kintone.com/en-us/industries/retail/)
          - [Education](https://www.kintone.com/en-us/industries/education/)
          - [Hospitality](https://www.kintone.com/en-us/industries/hospitality/)
          - [Healthcare](https://www.kintone.com/en-us/industries/healthcare/)
          - [Nonprofit](https://www.kintone.com/en-us/industries/nonprofit/)
    - [Solutions by Problem](https://www.kintone.com/en-us/problems/) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_plus.svg) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_back.svg) 
      
          - [Streamline Operations and Processes](https://www.kintone.com/en-us/problems/streamline-operations-and-processes/)
          - [Manage and Organize Business Data](https://www.kintone.com/en-us/problems/manage-and-organize-business-data/)
          - [Track Project Status and Accountability](https://www.kintone.com/en-us/problems/tracking-project-status-and-accountability/)
- [Customer Stories](https://www.kintone.com/en-us/customer-stories/)
- [Pricing](https://www.kintone.com/en-us/pricing/)
- Resources
  
   Resources![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_plus.svg)![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_back.svg) 
  
    - ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_plus.svg) ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_back.svg) 
      
          - [Webinars](https://www.kintone.com/en-us/events/)
          - [Guidebooks & Videos](https://www.kintone.com/en-us/guidebooks-and-videos/)
          - [Kintone Support Overview](https://www.kintone.com/en-us/support-overview/)
          - [Developers](https://kintone.dev/en/)
          - [Customer Resource](https://www.kintone.com/en-us/for-customers/)
          - [Blog](https://blog.kintone.com/business-with-heart?__hstc=181257784.34e49544339714832378568b4e02ab6c.1679463564667.1686561291068.1686624267650.55&__hssc=181257784.2.1686624267650&__hsfp=904488742)
- Company
  
   Company![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_plus.svg)![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_back.svg) 
  
    - - [About Us](https://www.kintone.com/en-us/company/)
          - [Careers](https://www.kintone.com/en-us/company/careers/)
          - [Press Center](https://www.kintone.com/en-us/press-center/)
          - [Contact Us](https://www.kintone.com/en-us/contact/)
- ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_search_black.svg)![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_search_red.svg)
  
  Search Kintone
  
  ![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_search_gray.svg)

![](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_login.svg)Log In

[Get a Free Trial](https://www.kintone.com/en-us/trial/)

[Get a Demo](https://resources.kintone.com/meetings/miri/kintonespecialist?__hstc=181257784.34e49544339714832378568b4e02ab6c.1679463564667.1686561291068.1686624267650.55&__hssc=181257784.2.1686624267650&__hsfp=904488742)

- [![](https://blog.kintone.com/hubfs/2018%20S2/assets/kin-heart-white.png) ![](https://blog.kintone.com/hubfs/2018%20S2/assets/kin-heart-grey.png) ![](https://blog.kintone.com/hubfs/2018%20S2/assets/kin-heart-red.png) Business with Heart \<3](https://blog.kintone.com/business-with-heart)
- [![](https://blog.kintone.com/hubfs/2018%20S2/assets/kin-heart-white.png) ![](https://blog.kintone.com/hubfs/2018%20S2/assets/kin-heart-grey.png) ![](https://blog.kintone.com/hubfs/2018%20S2/assets/kin-heart-red.png) Company + Product](https://blog.kintone.com/company-news)

- Business with Heart \<3Operations for the Digital First Team 
    - [Company + ProductLatest News from Kintone](https://blog.kintone.com/company-news)
    - [Business with Heart \<3Operations for the Digital First Team](https://blog.kintone.com/business-with-heart)

![A clinician and a front-desk coordinator work side by side: a submitted questionnaire and clinical record sit inside the EHR, while an open follow-up and a separate readiness decision sit in a coordination layer, linked by yellow arrows.](https://blog.kintone.com/hubfs/Blog%20Files/HCS6%20-%20Hero%20-%20Kintone-Style%20Healthcare%20Coordination%20Illustration.png)

[Workplace Productivity,](https://blog.kintone.com/business-with-heart/tag/workplace-productivity) [healthcare,](https://blog.kintone.com/business-with-heart/tag/healthcare) [Compliance,](https://blog.kintone.com/business-with-heart/tag/compliance) [Workflows,](https://blog.kintone.com/business-with-heart/tag/workflows)

# When Healthcare Workflows Don't Fit the EHR

Nov 20, 2026   |   by [Agbaje Feyisayo](https://blog.kintone.com/business-with-heart/author/agbaje-feyisayo)

[Tweet](https://twitter.com/share)

A new patient is booked for Thursday. By Tuesday, her intake questionnaire has come back through the patient portal, and her previous provider has faxed three years of records. The information has arrived, but two sections of the questionnaire are still blank, nobody has confirmed whether the outside records are complete, and the front desk can’t tell whether she’s ready.

Healthcare teams build spreadsheets and other workarounds beside the EHR to catch gaps like this. In a July 2026 MGMA Stat poll on EHR and practice-management workarounds, 75% of respondents said their clinicians frequently (43%) or sometimes (32%) use workarounds for EHR or practice-management issues, and respondents named intake among the areas where those workarounds happen. The poll drew 216 responses and was sponsored by NextGen Healthcare, an EHR vendor, so it describes these respondents and no one else.

Here is the short answer to where that work belongs. Clinical documentation and the authoritative patient record stay in the clinical system. Workflows built on cross-team follow-up, administrative approvals, and outside responses can run in a separate operational system when the existing EHR can’t support them, and only after its features have been checked first. EHR capabilities vary by vendor and configuration, and any workflow that handles patient information outside the EHR needs the right privacy, security, and contractual safeguards.

This article gives you a way to make that call, workflow by workflow. It follows one hypothetical organization, a 75-person community-based healthcare services provider onboarding new patients, through a decision that ends with a mixed answer: part of intake stays in the EHR, and part of it moves out.

## Why Healthcare Teams Build Workarounds Around the EHR

A workaround is a signal, and it points to one of several causes. Some are training problems: the EHR has a feature for the task, and nobody was shown it. Some are configuration problems: the system was set up for last year’s process. Some come from outside organizations whose faxes, portals, and emails never touch the EHR. Some point to a capability the system lacks. And some exist because nobody owns the step, so the spreadsheet becomes the owner by default.

A study of EHR workarounds in independent primary care practices found that same spread of causes, including workarounds driven by barriers to exchanging information with outside organizations. It’s a typology of causes, and it carries a useful warning: treating every workaround as a software failure leads straight to buying software for training and ownership problems.

![Diagram tracing one EHR workaround to five possible causes: a training gap, a configuration problem, an external handoff, a missing capability, and a step with no owner.](https://blog.kintone.com/hs-fs/hubfs/Blog%20Files/HCS6%20-1%20-%20healthcare_workaround_five_causes.png?width=1500&height=1080&name=HCS6%20-1%20-%20healthcare_workaround_five_causes.png)

Some of this work does sit outside the clinical record. There is a whole category of [operational work that neither the EHR nor the billing platform was built to manage](https://blog.kintone.com/business-with-heart/managing-the-work-your-ehr-doesnt), with its own requirements. The harder question, and the one this article answers, is which parts of a given workflow belong there and which belong back in the EHR.

## Which Workflows Belong in the EHR, and Which May Need Another System?

The table below gives starting points for assessment. None of them is a placement rule; each tells you where to look first and what to ask.

| **Workflow** | **Starting assumption** | **Question to investigate** |
| --- | --- | --- |
| Clinical documentation and care decisions | Keep in the clinical system | Would the change alter or duplicate an authoritative clinical record? |
| Intake questionnaires | Evaluate the EHR and patient portal first | Where do follow-up on incomplete answers and outside records get tracked? |
| [Referral processing](https://blog.kintone.com/business-with-heart/healthcare-referral-tracking-managing-the-loop-between-referral-and-appointment) | Evaluate existing EHR and practice-management features first | Where does the loop between referral and first appointment get closed, and who owns it? |
| [Prior authorization](https://blog.kintone.com/business-with-heart/how-to-track-prior-authorizations-without-losing-them-in-the-process) | Check EHR, billing, and specialist tools | Does outside coordination need its own accountable owner to keep authorizations from getting lost in the process? |
| Staff credentials and renewals | Evaluate HR, credentialing, and monitoring tools | Does an unresolved renewal affect scheduling? |
| DME and supply orders | The order lives in the EHR | Supplier follow-up and delivery confirmation often don’t: does the outside coordination have an owner, and does delivery status reach the clinician? |
| Equipment and non-clinical incident logs | Evaluate maintenance, safety, or operations tools | Are these records independent of patient care? |
| Quality improvement projects | Evaluate existing QI and reporting systems | Are owners, milestones, and evidence spread across teams? |
| Grant and program reporting | Evaluate the reporting environment | Does it combine data from several programs or functions? |

The pattern across the rows: who owns the workflow matters more than which department’s name is on it. A workflow that touches the patient record still has an owner for its follow-up, and that owner needs somewhere to work.

## Map the Work Before Choosing a Tool

Every workflow that crosses systems has three layers, and each can live somewhere different:

- **The authoritative record:** where the source information belongs. Patient, referral, and clinical data stay in the clinical system of record.
- **The working status:** the state of an unresolved action. Who owns the next step, what’s outstanding, and when it’s due.
- **The completion decision:** the authorized confirmation that the next step may proceed, with its evidence kept.

Problems start when the working status lives in an inbox or a spreadsheet while the authoritative record sits in the EHR, and nobody owns the gap between them. The tempting fix is to copy the patient record into another tool. That fix creates the next problem: two records that drift apart.

The layers line up with three separate acts: observe, record, authorize. Something arrives or happens. Someone records its status where the team works. An authorized person decides the next step may proceed. In the intake case, the submitted questionnaire arrives in the portal; the coordinator follows up on the blank sections and checks the outside records before recording intake as complete; the front-desk lead confirms the patient is administratively ready for the first visit. Administrative readiness means the practice’s intake requirements are met; whether the information is clinically sufficient stays with the clinician. A submitted form leaves intake incomplete until someone records it, and a tracker showing “complete” never decides clinical readiness.

Here is the organization’s intake process, mapped as it runs today:

| **Stage** | **Where the authoritative information lives** | **Where the working status lives** | **Who owns the next action** | **How the next person finds out** |
| --- | --- | --- | --- | --- |
| Trigger: questionnaire sent | EHR patient record and portal | The portal shows it sent | Intake coordinator | Portal notification (varies by EHR) |
| Open item: two sections blank | The questionnaire, in the EHR | The coordinator’s spreadsheet | Intake coordinator | Only if the coordinator checks |
| Outside response: prior records faxed | The EHR, once records are reviewed and filed | The fax tray and an email thread | Unclear | Someone notices the fax |
| Decision: is intake complete? | The EHR, for clinical content | Not recorded anywhere | The front-desk lead, informally | A hallway question |
| Completion: administratively ready for the first visit | The EHR | A note on the schedule | Front desk | The patient arrives |

The findings sit in the weak cells: “unclear,” “not recorded anywhere,” “only if the coordinator checks.” Each marks a handoff with no owner or no record, and none of them assumes new software is the fix. The records themselves need review before they count; the review of checking that records are complete before a case moves on is [its own process](https://blog.kintone.com/business-with-heart/healthcare-document-tracking-how-to-know-whats-missing-before-handoff).

Below the map, write the decision it points to. For this organization:

- **The unresolved handoff:** follow-up on incomplete answers and outside records, and the readiness call.
- **The system that stays authoritative:** the EHR, for the questionnaire, the records, and the health history.
- **Who owns the next action:** the intake coordinator for follow-up; the front-desk lead for administrative readiness.
- **What has to move between systems:** an intake-completion status and the minimum identifiers needed to match it to the scheduled visit, without copying clinical details.
- **The least complex change:** configure the EHR’s questionnaire reminders, record follow-up and readiness in one coordination layer, and update the schedule manually. The remaining risk is faxed records, which still need filing by hand. The intake coordinator role maintains the process.

To map your own process, pick one workflow that runs on email or a spreadsheet today, fill in the same five rows, and write the same decision block underneath.

## Configure, Use a Specialist Tool, Coordinate, or Integrate

Once the map shows where the gaps are, four tests decide what to do about each one. Ask them in order, because each one brings different requirements and responsibilities.

| **Test, in order** | **Question** | **Outcome if yes** | **What goes wrong** |
| --- | --- | --- | --- |
| 1. Existing capability | Can the EHR or practice-management system support this through configuration, training, or existing integrations? | Configure the existing system | Customization that drifts from the real process |
| 2. Specialist requirement | Does the work need capabilities a general coordination tool shouldn’t recreate, such as credential verification or revenue-cycle functions? | Use a purpose-built tool | Another silo, unless its status reaches the people who depend on it |
| 3. Operational coordination | Is the main gap ownership, deadlines, visibility, and follow-up across teams? | Coordinate in a separate application | Duplicate records, conflicting statuses, or patient data without the right agreements |
| 4. Information exchange | Must systems exchange information reliably and repeatedly for the process to work? | Integrate where justified | Interfaces nobody owns or monitors |

Run intake through them. Test 1 passes for the questionnaire: the EHR’s portal already sends, collects, and stores it, so the fix is configuration, such as automatic reminders for unanswered sections. Test 2 doesn’t apply; no specialist tool owns intake follow-up. Test 3 passes for everything around the questionnaire: chasing the blank sections, tracking the faxed records, and recording readiness need an owner, a due date, and a status the front desk can see. Test 4 asks how readiness reaches the schedule, and for a few new patients a week, a staff member updating the schedule by hand is enough. The answer is mixed: configure the EHR for one part, coordinate the rest separately, and integrate nothing yet.

The same four tests give a different answer for DME and supply orders. The order belongs in the EHR (test 1). The supplier’s own portal may already track the shipment (test 2), so there’s no reason to rebuild that. The follow-up, the delivery confirmation, and the call to the patient need an owner (test 3). And whether delivery status should flow back into the EHR automatically is a real integration question, especially at volume (test 4). Same method, different outcome: a sign the method judges each workflow on its own terms.

Integration itself is a spectrum. Work can connect through a manual update, a secure notification, an approved interface, or an automated exchange. Frequency, timeliness, sensitivity, reliability, and who owns the connection decide which fits. Many cross-system workflows at small and midsize organizations need no API or FHIR integration at all; a controlled manual handoff is right for a low-volume process, and an interface that nobody monitors is worse than none. FHIR is HL7’s standard for exchanging healthcare information, and supporting the standard doesn’t by itself produce a working integration: someone still has to design, test, and monitor the connection.

The answer can combine approaches, and “no new software” is a legitimate result. If the map shows that the gap is a feature nobody configured, the fix is configuration or training, with no new purchase.

## What Changes When Administrative Work Contains Patient Information

Intake data is protected health information, and calling a workflow administrative doesn’t change that. Patient names, appointment dates, referral details, and authorization records can all be PHI. Moving any of it into a separate cloud service brings HIPAA with it: under [HHS guidance on cloud services that handle ePHI](https://www.hhs.gov/hipaa/for-professionals/special-topics/health-information-technology/cloud-computing/index.html), the service needs a business associate agreement and appropriate safeguards. A separate application never sidesteps those obligations by being separate.

The map helps here too, because it shows what each team actually needs. The front desk’s “intake complete” status can carry no clinical detail at all: a patient identifier, a visit date, and a yes. That identifiable status is still PHI, so minimizing it reduces exposure without removing the obligations. Billing needs the insurance details. The clinician needs the full history, which stays in the EHR. Design the coordination layer around the least information each view requires, and the privacy question gets smaller before anyone signs anything.

![A healthcare operations staff member reviews a screen showing one EHR patient record feeding three role-based views: front desk, billing, and clinician, each limited to the information that role needs.](https://blog.kintone.com/hs-fs/hubfs/Blog%20Files/HCS6%20-2%20-%20Aha%20Moment_%20Healthcare%20Workflow%20Clarity.png?width=1536&height=1024&name=HCS6%20-2%20-%20Aha%20Moment_%20Healthcare%20Workflow%20Clarity.png)

When a coordination layer does hold PHI, check the vendor’s position directly. Kintone, for example, supports HIPAA-regulated workflows under its applicable security and contractual arrangements, has undergone a SOC 2 Type 2 examination, and is ISO/IEC 27001 certified. Organizations that process or store PHI in Kintone must execute a Business Associate Agreement and put appropriate safeguards in place for their own use. Your own compliance review decides what the workflow may hold and who may see it.

## How a Connected Operations Layer Works Alongside the EHR

Back to intake, with the decision made. The three layers now each have a home.

- **The authoritative record stays in the EHR:** the questionnaire, the prior records once filed, and the health history.
- **The working status moves to a coordination layer:** one record per new patient, holding the open follow-up, its owner and due date, and the status of the outside records.
- **The completion decision is recorded by an authorized person:** the front-desk lead marks the patient administratively ready for the first visit, and the record keeps who decided and when.

The coordination record carries no copy of the clinical content. It points to the EHR for that, and it shows each team only its own view: the front desk sees ready or not ready, the coordinator sees what’s outstanding, and billing sees the insurance status.

Kintone is one way to run that layer. An intake follow-up app holds one record per new patient. Process Management moves each record through its statuses, with an assignee at each step, so the coordinator owns follow-up and the front-desk lead owns the administrative readiness decision. Reminder notifications prompt the coordinator before the visit date when a record is still open. Field permissions give each team its own view of the same record. Getting readiness into the EHR’s schedule stays a manual update, or a separately designed and verified integration if volume justifies it; no connection to the EHR is assumed.

## When a Separate Workflow Application Creates More Problems

A separate application solves a coordination gap. It also creates new work, and sometimes the new work costs more than the gap. Stop and reconsider when any of these is true:

- **It would duplicate patient data.** If the plan needs a second copy of the clinical record to function, the two copies will drift, and someone will act on the wrong one.
- **An EHR feature already fits.** If test 1 passes and nobody has tried configuring the existing system, configure it first.
- **Nobody owns synchronization.** Any status that has to match between two systems needs a named person or a monitored process keeping it matched.
- **Statuses would conflict.** If the EHR and the new tool can each say a patient is ready, decide which one wins before launch, or staff will act on whichever one they checked last.
- **The data handling isn’t authorized.** Without a business associate agreement and a compliance review covering what the tool holds, the project waits.
- **There’s no completion and escalation process.** A new tool with no rule for who closes an item, and what happens when it stalls, moves the spreadsheet’s problems to a new screen.

Any one of these is a reason to pause and look first at the EHR, a process change, or a clearer owner.

## What Your Map Tells You to Require

If the decision sequence points to a coordination layer, your completed map has already written most of your requirements. Turn the decision block into five questions any tool has to answer before you buy it:

1. **What stays authoritative, and what must the tool never duplicate?** For intake: the questionnaire and the health history stay in the EHR, so the tool holds references and statuses only.
2. **Which teams need which views?** For intake: the front desk sees ready or not ready, the coordinator sees what’s outstanding, and billing sees insurance status. Permissions have to enforce each view; hiding a column is too weak.
3. **How does information move, and at what integration level?** For intake: a manual readiness update today, with an interface considered only when volume justifies one and someone owns it.
4. **Who owns maintenance and escalation?** For intake: the coordinator role maintains the workflow, and the front-desk lead takes items that stall past the visit date.
5. **What patient information will it hold, and what safeguards does that require?** For intake: identifiers and statuses, which still means a business associate agreement and a compliance review.

These five come from your own process, so they test the tool against the work you actually do. The broader requirements for any operational layer, such as aging logic, structured history, and management visibility, still apply alongside them.

![Diagram showing a healthcare intake workflow map being converted into software requirements, which are then used to evaluate a potential coordination platform.](https://blog.kintone.com/hs-fs/hubfs/Blog%20Files/HCS6%20-3%20-%20Workflow%20Map%20to%20Vendor%20Test.png?width=1536&height=1024&name=HCS6%20-3%20-%20Workflow%20Map%20to%20Vendor%20Test.png)

Map one workflow before you buy anything. Then bring the map and book a demo with a Kintone expert to see where your workflow’s coordination layer could live.

[![Kintone Free Trial CTA](https://no-cache.hubspot.com/cta/default/1857320/a0c9f62e-cc45-42e5-ade0-913fa2ddcd53.png)](https://cta-redirect.hubspot.com/cta/redirect/1857320/a0c9f62e-cc45-42e5-ade0-913fa2ddcd53)

[![](https://blog.kintone.com/hubfs/fe.png)](https://blog.kintone.com/business-with-heart/author/agbaje-feyisayo)

About the Author

[Agbaje Feyisayo](https://blog.kintone.com/business-with-heart/author/agbaje-feyisayo)

Agbaje Feyisayo is a dynamic content marketing expert with over 10 years of experience writing high-converting content across SaaS, technology, AI, and digital transformation. With a strong background in product marketing and storytelling, Agbaje helps top-tier companies turn complex ideas into actionable content that attracts and converts leads.

 Recommended Posts

 Up Next

<https://blog.kintone.com/>

 Previous

[How to Evaluate Workflow Software: A Software Selection Guide](https://blog.kintone.com/business-with-heart/how-to-evaluate-workflow-software/)

[Back to Business with Heart \<3 Blog Page](https://blog.kintone.com/business-with-heart)

### Subscribe to Blog

#### Recommended Posts

[![An operations lead holds a written criteria sheet before a vendor presentation begins, with a connector showing the criteria will judge the demo.](https://blog.kintone.com/hubfs/CGA-5%20-%20Hero%20-%20Criteria%20Mapping%20to%20App%20Screen.png)](https://blog.kintone.com/business-with-heart/how-to-evaluate-workflow-software/) 

 Workplace Productivity

##### How to Evaluate Workflow Software: A Software Selection Guide

 Everyone agrees the software looks good, but has anyone asked whether it solves the problem your team actually has? The product looks finished, the presenter knows every shortcut, and the sample data fits perfectly. If your team hasn't written down what it nee... 

[Read More »](https://blog.kintone.com/business-with-heart/how-to-evaluate-workflow-software/)

[![Illustration of a woman at her desk picturing a request moving between three colleagues, with one item flagged as incomplete and a loop that sends the request back before it reaches approval.](https://blog.kintone.com/hubfs/Blog%20Files/workflow-intake-process-hero.webp)](https://blog.kintone.com/business-with-heart/workflow-intake-process) 

 Improving Teamwork

##### Why Do Cross-Departmental Processes Break Before They Start?

 A purchase request reaches finance without a cost center. A new-vendor setup request reaches procurement without the vendor's tax ID. A customer escalation reaches engineering without the steps to reproduce the problem. In each case, the receiving team stops, ... 

[Read More »](https://blog.kintone.com/business-with-heart/workflow-intake-process)

[![A billing reviewer compares an incoming case containing a service note and provider order against three required documents. The supporting report has no matching file in the case.](https://blog.kintone.com/hubfs/HC-S4%20-%20Hero%20-%20Document%20Handoff%20and%20Missing%20Report.png)](https://blog.kintone.com/business-with-heart/healthcare-document-tracking-how-to-know-whats-missing-before-handoff) 

 Workplace Productivity

##### Healthcare Document Tracking: How to Know What’s Missing Before Handoff

 A billing reviewer opens a case marked ready and has to send it back. One supporting record has not arrived from the provider, and another has been received without anyone checking that it meets the requirement. The attachments are accessible, but the handoff ... 

[Read More »](https://blog.kintone.com/business-with-heart/healthcare-document-tracking-how-to-know-whats-missing-before-handoff)

### Try Kintone For Free!

Our clients have built and deployed over 340,000 Kintone applications. Join them by signing up for a free trial–no credit card required–or scheduling a customized product demo.

[![Try Kintone for free](https://no-cache.hubspot.com/cta/default/1857320/38781637-01ae-4d81-a227-bf6704b72577.png)](https://cta-redirect.hubspot.com/cta/redirect/1857320/38781637-01ae-4d81-a227-bf6704b72577)[![Schedule a Live Demo](https://no-cache.hubspot.com/cta/default/1857320/97cabdc7-d654-44b7-bf14-68222b115553.png)](https://cta-redirect.hubspot.com/cta/redirect/1857320/97cabdc7-d654-44b7-bf14-68222b115553)

[![Kintone](https://blog.kintone.com/hubfs/KintoneGlobal/svg/logo_kinton_black.svg)](https://www.kintone.com/en-us/)

 U.S.  Cambodia  China(中文)  Hong Kong  India  Indonesia  Korea  Laos  Malaysia  Myanmar  Philippines  Singapore  Taiwan(繁体字)  Thailand  Viet Nam  Japan(日本語)  Australia  Fiji  Kiribati  New Zealand  Papua New Guinea  Samoa  Solomon Islands  Tonga  Tuvalu  Vanuatu

- [![facebook](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_facebook.svg) ![facebook](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_facebook_color.svg)](https://www.facebook.com/kintoneusa)
- [![twitter](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_x.svg) ![twitter](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_x_color.svg)](https://x.com/kintone)
- [![LinkedIn](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_linkedin.svg) ![LinkedIn](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_linkedin_color.svg)](https://www.linkedin.com/company/kintoneusa/)
- [![Instagram](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_instagram.svg) ![Instagram](https://blog.kintone.com/hubfs/KintoneGlobal/svg/icon_instagram_color.svg)](https://www.instagram.com/kintoneusa/)

- [Terms of Use](https://www.kintone.com/en-us/terms-of-use/)
- [Security](https://www.kintone.com/en-us/security/)
- [Contact Us](https://www.kintone.com/en-us/contact/)

- [Privacy Policy](https://www.kintone.com/en-us/privacy-policy/)
- [Partners](https://www.kintone.com/en-us/partners/)

 Do Not Sell or Share My Personal Information

- [Solutions by Department](https://www.kintone.com/en-us/departments/)
  
    - [Operations](https://www.kintone.com/en-us/departments/business-operations/)
    - [Sales](https://www.kintone.com/en-us/departments/sales/)
    - [Customer Support](https://www.kintone.com/en-us/departments/customer-support/)
    - [HR & Admin](https://www.kintone.com/en-us/departments/hr-admin/)
    - [Marketing](https://www.kintone.com/en-us/departments/marketing/)
    - [Manufacturing & Retail Management](https://www.kintone.com/en-us/departments/manufacturing-retail-management/)
    - [IT Support](https://www.kintone.com/en-us/departments/it-support/)
- [Solutions by Function](https://www.kintone.com/en-us/functions/)
  
    - [Convert spreadsheets to databases](https://www.kintone.com/en-us/functions/convert-spreadsheets-to-databases/)
    - [Data Management](https://www.kintone.com/en-us/functions/data-management/)
    - [CRM & Sales Management](https://www.kintone.com/en-us/functions/crm-sales-management/)
    - [Project Management](https://www.kintone.com/en-us/functions/project-management/)
    - [Workflow Management](https://www.kintone.com/en-us/functions/workflow/)
    - [Remote Work](https://www.kintone.com/en-us/functions/remote-work/)
    - [Recruitment & Hiring](https://www.kintone.com/en-us/functions/recruitment-hiring/)
- [Solutions by Industry](https://www.kintone.com/en-us/industries/)
  
    - [Manufacturing](https://www.kintone.com/en-us/industries/manufacturing/)
    - [Real Estate](https://www.kintone.com/en-us/industries/real-estate/)
    - [Retail](https://www.kintone.com/en-us/industries/retail/)
    - [Education](https://www.kintone.com/en-us/industries/education/)
    - [Hospitality](https://www.kintone.com/en-us/industries/hospitality/)
    - [Healthcare](https://www.kintone.com/en-us/industries/healthcare/)
    - [Nonprofit](https://www.kintone.com/en-us/industries/nonprofit/)
- [Solutions by Problem](https://www.kintone.com/en-us/problems/) 
  
    - [Streamline Operations and Processes](https://www.kintone.com/en-us/problems/streamline-operations-and-processes/)
    - [Manage and Organize Business Data](https://www.kintone.com/en-us/problems/manage-and-organize-business-data/)
    - [Track Project Status and Accountability](https://www.kintone.com/en-us/problems/tracking-project-status-and-accountability/)

- [Customer Stories](https://www.kintone.com/en-us/customer-stories/)
- [Pricing](https://www.kintone.com/en-us/pricing/)
- [Native Kintone Plug-ins](https://www.kintone.com/en-us/features/plugins/)

- [Intro to Kintone](https://www.kintone.com/en-us/intro/)
- [Why Kintone](https://www.kintone.com/en-us/why-kintone/)
- [Customer Stories](https://www.kintone.com/en-us/customer-stories/)
- [Pricing](https://www.kintone.com/en-us/pricing/)

- [How Kintone Works](https://www.kintone.com/en-us/how-kintone-works/)
- [App Template Library](https://www.kintone.com/en-us/features/app-templates/)
- [Extensions](https://www.kintone.com/en-us/features/extensions/)
- [Native Kintone Plug-ins](https://www.kintone.com/en-us/features/plugins/)
- [Kintone AI](https://www.kintone.com/en-us/features/ai/)
- [System Administration](https://www.kintone.com/en-us/features/administration/)
- [Security](https://www.kintone.com/en-us/security/)

- [Webinars](https://www.kintone.com/en-us/events/)
- [Guidebooks & Videos](https://www.kintone.com/en-us/guidebooks-and-videos/)
- [Kintone Support Overview](https://www.kintone.com/en-us/support-overview/)
- [Developers](https://kintone.dev/en/)
- [Customer Resource](https://www.kintone.com/en-us/for-customers/)
- [Blog](https://blog.kintone.com/business-with-heart)

- [About Us](https://www.kintone.com/en-us/company/)
- [Careers](https://www.kintone.com/en-us/company/careers/)
- [Press Center](https://www.kintone.com/en-us/press-center/)
- [Terms of Use](https://www.kintone.com/en-us/terms-of-use/)
- [Privacy Policy](https://www.kintone.com/en-us/privacy-policy/)
- [Partners](https://www.kintone.com/en-us/partners/)
- [Contact Us](https://www.kintone.com/en-us/contact/)
- Do Not Sell or Share My Personal Information

© 2022 Kintone

© 2022 Kintone

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Agbaje Feyisayo",
    "url" : "https://blog.kintone.com/business-with-heart/author/agbaje-feyisayo"
  },
  "dateModified" : "2026-11-20T14:30:01.097Z",
  "datePublished" : "2026-11-20T14:30:01.000Z",
  "headline" : "EHR Workarounds: When Healthcare Workflows Don't Fit the EHR",
  "image" : [ "https://blog.kintone.com/hubfs/Blog%20Files/HCS6%20-%20Hero%20-%20Kintone-Style%20Healthcare%20Coordination%20Illustration.png" ],
  "mainEntityOfPage" : {
    "@id" : "https://blog.kintone.com/business-with-heart/ehr-workarounds-healthcare-workflows",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://blog.kintone.com/hubfs/KIN_Logo_H_clr_p_web-4.png"
    },
    "name" : "kintone"
  }
}
```