Moving records from another system?
Start with an export from your current system and your current caseload. The guide to switching explains how to plan a safe move.
Integrations
The child record is where the facts live. Sign-in, billing, email, and EI Hub files each have one path. Each path says what data moves, in which direction, and who is responsible.
You send claim files to EI Hub and bring back acknowledgments and payments. Each claim keeps one history.
File you upload
Create 837P files from verified claims. Mark the file when the agency uploads it to EI Hub.
File you upload
Upload acknowledgment files. Each response stays linked to the claim it answers.
File you upload
Upload payment CSV files and match each payment to the claim it pays.
Every way of logging in follows the same agency security settings.
Your agency sets it up
A sign-in provider your agency sets up opens the same account. A person never has a second account.
Built in
Log in with your device instead of a password. Two-step verification is the backup.
Each outside service gets only what its job needs.
Built in
Handles billing for the agency's subscription. Child records and EI Hub claim details never go to Stripe.
Built in
Carries sign-in and account messages only. It never contains child or family information.
Built in
Suggests postal addresses as you type. Only the address you choose is saved.
Getting your data
Tiny Solutions does not offer a public API yet. To get data out today, use agency exports and the file connections above.
Start with an export from your current system and your current caseload. The guide to switching explains how to plan a safe move.
Tell us the other system, which way the data moves, how often, and who owns it. Do not include real child data.
It is easier to choose the right connection after your child records are in place.