Imports and integrations
Your data comes in as CSV. That is the whole answer.
ShiftNote has no API connection to any care-management system. We would rather tell you that on this page than have you discover it in an implementation call, so here is exactly what we can read, what we cannot, and what a CSV import actually handles.
What exists today
Available means in production and you can use it now. Planned means not built — not next quarter, not in beta, not built.
| Capability | Status | Detail |
|---|---|---|
| CSV claim import | Available | Export claims from whatever system you run and import them. This is how every provider gets data in today. |
| Manual claim entry | Available | For a handful of claims, or for testing the assessment on a few examples first. |
| Notes written in ShiftNote | Available | Workers write notes here and copy them into your system. Notes written here are already linked to your organisation. |
| Notes pasted in from another system | In progress | Records can be brought in, but there is no bulk note importer with field mapping yet. For an Evidence Exposure Report we handle this with you. |
| Saved import mappings | Planned | Your column mapping is confirmed each time rather than remembered between imports. |
| API access | Planned | There is no public API. Nothing authenticates against ShiftNote from outside, and no third-party system can read or write your data. |
| Direct connections to care-management systems | Planned | No connector exists to any care-management, rostering or finance system. If you see us listed as an integration partner anywhere, it is not accurate and we would like to know. |
If CSV is the only door, it had better be a good one
This is the one path that touches a provider's financial export, so it is written by hand rather than delegated to a library, and it is the most heavily tested code in the product.
Header auto-detection
Your export’s column names are matched to the fields we need. You confirm the mapping before anything is written.
Browser-side preview
Validation runs in your browser using the same code the server writes with, so you see exactly what will land before the file leaves your machine.
Day-first dates, confirmed not guessed
03/04/2027 is 3 April in Australia and 4 March in the United States, and reading it wrong moves the claim deadline by a month. Ambiguous dates are counted and shown to you with real examples from your file; the import refuses to proceed until you confirm.
Exact currency handling
Amounts are parsed as decimals rather than floating point, because parsing $0.145 as a float and rounding loses a cent per row on a financial import.
Whole-row validation
A row with any error is excluded entirely rather than part-imported. Half a claim line corrupts both the exposure figure and the deadline clock.
Safe re-import
Re-importing a corrected file updates the rows it matches rather than duplicating them, so a fix cannot double-count your claims.
Messy file tolerance
Quoted fields with embedded commas and newlines, escaped quotes, CRLF, the Excel byte-order mark, and semicolon or tab delimiters. Ragged rows are reported, never silently dropped.
Working alongside the system you already run
This is a workflow statement, not a technical one, and the difference matters.
Providers run ShiftNote next to whatever care-management, rostering or finance software they already have. Claims come out of that system as an export and go into ShiftNote; notes written in ShiftNote go back the other way by copy and paste. Nothing syncs, nothing is kept in step automatically, and nothing breaks in your system if you stop using ours.
That is what “works alongside” means here. It is not an integration and we do not describe it as one.
The upside of that boundary: there is nothing to install, no vendor to get permission from, and no project. A provider can run their first exposure assessment on an export they already know how to produce.
Want a connection to a specific system?
Telling us which one, and how many providers need it, is what decides the order these get built in.
Email info@shiftnote.com.au with the system you run and roughly how many workers use it. We will tell you honestly whether it is on the list and when — including “not this year”, which is the current answer for most of them.
Everything on this page is also reflected on our trust centre, which lists every subprocessor that touches your data and where each one processes it.