Skip to content
CRIS

CRIS CONNECT / DATA HUB

Before CRIS can give you reliable answers, it needs reliable data.

Revenue-cycle information often comes from several places.

One system may contain claims. Another may contain payments. Another may contain denials. Someone may still be sending spreadsheets.

CRIS Connect gives your organisation a controlled way to bring that information into CRIS, check it, understand it and confirm that what arrived is what you expected.

CRISConnect / Data HubImport review
Source fileclaims_2026_09.xlsx
Approved sourceBilling export
Ready for review
01Source File25,000 rows
02Profile18 fields
03Map18 matched
04Validate31 exceptions
Import readinessCurrent review
Nothing becomes trusted CRIS data simply because it was uploaded.
01Know where the data came from.
02Understand what it contains.
03See what needs review.
04Confirm what CRIS accepted.

CONTROL BEFORE ANALYSIS

Bad data does not always look bad.

A spreadsheet can open perfectly and still contain a problem.

A column can have the wrong meaning. A date can be interpreted incorrectly. A claim can appear twice. A required field can be missing.

The report looks professional, but the information underneath it may already be wrong.

CRIS Connect is designed to put controls before analysis.

Source ProfileWhat changed before this file moves forward?
Review required
Rows received25,000Expected range met
Fields detected181 renamed field
Empty required values19Needs correction
Potential duplicates8Needs decision
Source structure comparisonPrevious vs current
Claim_IDMatched
Service_DateMatched
Payer_NameRenamed
Billed_AmountMatched
Authorization_NoNew

UNDERSTAND THE SOURCE

Uploading the file is only the beginning.

A normal upload process asks: “Did the file upload?”

CRIS Connect asks more important questions.

01

See what is inside the data before relying on it.

When a new source file arrives, CRIS can examine its structure before the information is accepted for normal use.

You should not have to discover a changed spreadsheet format because a dashboard suddenly stops making sense.

Field profile18 detected fields
Claim_ID100%
Service_Date99.9%
Payer_Name100%
Billed_Amount100%
Authorization_No84%

19 required values are missing across the file.

Validation & duplicate protectionFind problems before they become reporting problems.
31 exceptions
Exceptions by typeCurrent file
Missing claim identifier11 recordsReject before import
Missing service date8 recordsNeeds correction
Potential duplicate claim8 recordsNeeds decision
Date cannot be understood4 recordsNeeds correction

VALIDATE & PROTECT

Do not let the same data quietly enter twice.

Duplicate information can create misleading results.

If the same claim file is imported twice, totals can appear larger than they really are. If the same payment is loaded more than once, revenue can be overstated.

CRIS Connect is designed to help identify potential duplicate records and repeat submissions before they contaminate the wider dataset.

The purpose is not to reject everything that looks unusual. It is to make unusual conditions visible so they can be reviewed before they quietly become part of the organisation's reporting.

PREVIEW FIRST. COMMIT SECOND.

See what will happen before you commit the import.

One of the most important controls in CRIS Connect is the ability to check an import before making it final.

Think of it as a rehearsal.

CRIS can show what it expects to accept, reject or flag before the information becomes part of the working dataset.

Preview first. Commit second.

Dry Run SummaryImport impact before approval
Ready with exceptions
Source records12,450
Ready to accept12,431
Rejected11
Potential duplicates8
Total source amount$4.82M
Amounts reconcile
Total accepted amount$4.82M
Record reconciliationSource vs outcome
12.5K10K5K0SourceAcceptedRejectedDuplicates 12,45012,431118

CONTROLLED INTAKE

From source file to trusted CRIS data.

The CRIS Connect journey can be understood in eight simple stages.

  1. 01ReceiveBring approved source information into CRIS.
  2. 02UnderstandSee what the file contains before relying on it.
  3. 03MatchConnect source fields to the information CRIS understands.
  4. 04CheckIdentify missing, invalid or unusual information before it moves forward.
  5. 05ProtectRecognise information that may contain sensitive patient data.
  6. 06Prevent duplicationCheck whether information may already exist before accepting it again.
  7. 07PreviewSee what the import will do before making the change final.
  8. 08ConfirmReconcile the result and retain a history of what happened.
Import HistoryEvery import should leave a trail.
Reconciled
claims_2026_09.xlsxSep 18, 2026 · 10:42 AM
Import CR-260918-014
  1. ReceivedApproved billing source · 25,000 records
  2. Profiled & mapped18 fields detected · 18 mapped
  3. Validation reviewed31 exceptions reviewed before approval
  4. Import approvedAuthorised import decision recorded
  5. ReconciledRecord counts and financial totals confirmed

TRACEABILITY

Every import should leave a trail.

Months later, somebody may ask: Where did this information come from? Who imported it? When was it loaded? Were any records rejected? Was the import reconciled?

CRIS Connect keeps import history so the organisation can look back at previous data loads and understand what happened.

This helps turn data movement into a controlled business process rather than a collection of files sitting in folders.

WHY THIS MATTERS TO MANAGEMENT

Better management information begins with better-controlled source information.

A senior executive may never personally import a spreadsheet. But the quality of that import can eventually affect what the executive sees.

A mistake at the beginning can become a misleading KPI, an incorrect trend, a false revenue variance, an inaccurate outstanding balance or an unnecessary investigation.

Source controlWhat CRIS Connect protects downstream
Source fileChecked
MappingGoverned
ValidationReviewed
ReconciliationConfirmed
Management KPIsTrend analysisOutstanding balancesRevenue investigation

THE DIFFERENCE

The difference is not the upload. It is the control around the upload.

A basic import tool says:

Choose File → Upload

CRIS Connect is designed to answer the questions that determine whether the information should be trusted.

Where did the file come from? What information does it contain? Has CRIS understood it correctly? Is anything missing? Is sensitive information present? Have we seen these records before? What will happen if we proceed? Did the final result agree with the source? Can we prove what happened later?

CRIS CONNECT / DATA HUB

Good intelligence starts with data you can account for.

CRIS Connect provides the controlled path between your source systems and the wider CRIS platform.

Receive it. Understand it. Check it. Protect it. Reconcile it. Then use it.