Unlocking The Power Of Ohiohealth Esource Sharepoint Enhancing Collaboration And Productivity

Getting OhioHealth Esource SharePoint Working Without Losing Your Mind

I spent about three weeks figuring out how our department actually used the eSource SharePoint platform at OhioHealth. Most people just accept that documents live somewhere in the cloud and hope they turn up when needed. That approach works until you have six people editing the same template and suddenly the permissions structure breaks something nobody noticed for months. The basic setup starts with understanding what eSource actually means in this context. It is not a standalone product you download and install. OhioHealth built it as a SharePoint-based document management system for clinical research teams to store source documents, protocols, and regulatory files in one place. The name comes from electronic source data tracking.

Unlocking The Power Of OhioHealth ESource SharePoint Enhancing Collaboration And Productivity

Here is what most people miss when they start using eSource. The default permission inheritance on modern SharePoint sites creates a situation where site owners accidentally grant contributor access to entire departments instead of individual team members. I learned this the hard way when a quality improvement project got flagged because three researchers outside our core team could edit protocol amendments without going through IRB review first. That incident took about four days to untangle and cost us two weeks of documentation cleanup. The workaround involves turning off inherited permissions at the library level and setting custom access groups. You navigate to Library Settings, then Advanced Settings, and switch inheritance off. Then you create SharePoint groups called something like "eSource Reviewers Only" instead of using the generic Contributors group. I keep three access tiers: Viewers who can only read, Editors who can upload and modify, and Approvers who sign off on final versions. This takes maybe twenty minutes per library but prevents the kind of audit finding I described. Version control in SharePoint works differently than people expect from desktop applications. Every time someone saves a document, SharePoint creates a new version automatically. The default setting keeps about five hundred versions per file before it purges the oldest ones. That is usually plenty for clinical research, but it means you can recover documents people thought were lost permanently. I recovered a protocol revision from version forty-two once after someone checked "delete" instead of "save as new version."

The metadata structure is where most teams get stuck. SharePoint libraries need column definitions before people start uploading files, or you end up with documents that have no way to be filtered properly. I set up five required columns for our research library: Study ID, Document Type, Version Number, Review Date, and Principal Investigator. Getting those configured takes about an hour upfront but saves researchers twenty minutes per document search afterward. Without metadata, your SharePoint library is just a folder with a fancy name. Checkout versus check-in is another area that causes problems. When someone checks out a document, other users can see it but cannot edit it until the check-out is released. This prevents overwriting conflicts but annoys people who forget to check files back in. I recommend enabling checkout for final version documents only, not drafts. Drafts should live in a separate folder where people can work freely without worrying about check-out status. The search functionality in SharePoint is actually decent once you understand how the search schema works. By default, SharePoint indexes document content, metadata, and file names. But it does not index handwritten notes or images inside PDFs unless you enable content extraction. Our team uses this for scanned consent forms, and about thirty percent of our searchable documents come from extracted image text now instead of file names alone. This requires enabling content extraction in the SharePoint admin center, which takes about ten minutes and runs overnight for indexing.

What Happens When Things Break

eSource SharePoint has some real limitations that nobody warns you about. The platform struggles with large batch uploads. If you try to move more than five hundred files into a library at once using the web interface, it times out about half the time. I use PowerShell scripts for bulk operations instead, and the same upload that fails on the website completes in about twelve minutes through the command line. There are open source scripts available online if you need them. Another problem is the mobile experience. The SharePoint mobile app is functional but slow for anything involving document editing or metadata updates. Researchers on the go usually end up using the web version in Safari or Chrome mobile instead, and those pages load about four seconds slower than on desktop. I accept this limitation because field researchers need access even if it is not perfect. The audit logging feature is another area where expectations don't match reality. SharePoint does track who accessed or modified documents, but the logs are stored in Microsoft 365 audit logs, not inside SharePoint itself. Accessing those logs requires going through the Microsoft Purview compliance portal, and the data is only available for about ninety days by default. Our compliance team extended retention to one year, which adds about fifty dollars monthly to our licensing costs. Worth it for clinical research, but you should budget for it.

Collaboration features like co-authoring work well for Microsoft Office documents but break down completely for PDFs and image files. Two people cannot edit the same PDF simultaneously, so your team ends up with version confusion when people download, edit locally, and reupload without updating the document name. I solved this by creating a naming convention that includes the date and editor initials in every filename. It looks ugly but eliminates the version disputes that used to happen weekly.

Practical Setup Steps

Setting up a new eSource library from scratch takes about four hours if you do it right. Start by creating the SharePoint site with the appropriate template, then configure metadata columns before anyone uploads files, set up permission groups, create document templates with the required fields pre-filled, and finally train your team on the checkout process and naming conventions. Rushing through this setup because you want the library ready by Friday usually results in about three weeks of cleanup later. Document template creation is important. Most research teams do not create templates and waste time formatting every new document from scratch. I create four standard templates: Protocol Amendment, Informed Consent Form, Case Report Form, and Monitor Visit Report. Each template has the required metadata columns pre-populated with default values like the study ID format and document type. Creating these templates takes about thirty minutes total but saves the team at least ten minutes per new document. The review workflow in SharePoint can be set up using Power Automate without writing any code. I created a simple approval flow where any document uploaded to the "Under Review" folder automatically sends an email to the designated approver with a link to the document. The approver can either approve or reject with comments, and the document moves to "Approved" or "Revision Requested" accordingly. Setting up this flow takes about an hour in Power Automate but eliminates the manual email chasing that used to take up about two hours weekly.

Training materials should be minimal and practical. I created a two-page reference document that covers the five most common tasks: uploading a document, checking out a file, updating metadata, searching by study ID, and requesting access to another team's library. People rarely read more than that, and the rest they figure out through trial and error. I keep the reference document on the SharePoint homepage so it is always visible. The backup strategy deserves more attention than it gets. SharePoint has built-in retention policies that delete documents after a set period, but those policies can be overridden by individual users. I set a library retention policy that keeps all documents for seven years, matching our clinical research retention requirements. This policy cannot be overridden by individual users, only by site administrators with special permissions. Setting this up takes about fifteen minutes in the SharePoint admin center. Integrating eSource with other systems like REDCap or Oracle Clinical requires careful planning. Most teams try to sync data automatically between systems, but this usually creates more problems than it solves because the data formats do not match perfectly. I recommend manual exports and imports on a monthly basis instead, and keeping a simple spreadsheet that tracks when each data pull happened. This takes about thirty minutes monthly but ensures data accuracy without the integration headaches.

Security considerations should include regular access reviews. I recommend reviewing library permissions quarterly, which takes about an hour per library, to make sure people who left the project or changed roles no longer have access. I found three former team members with active contributor access during my first quarterly review, and removing them prevented potential data exposure. This is a small time investment that pays off during audits. The overall system works well once you understand its quirks and limitations. It is not a perfect solution for every clinical research documentation need, especially if you require real-time co-authoring on PDFs or deep integration with external systems. But for document storage, version control, and basic collaboration across research teams, it handles the job adequately and integrates with the Microsoft ecosystem that most healthcare organizations already use. The learning curve is steeper than commercial document management products, but the cost savings and institutional control make it worthwhile for OhioHealth and similar organizations.