Skip to content
View packages

GoSeedly Home Health Agency Kit / INSTALLATION

A clear path
to your workspace.

Bring the kit into your compatible Seedly installation, preserve existing work, and choose the starter content that fits your team.

01

Start with your Seedly project.

Use your separately obtained Seedly CRM 5.8.4 installation with extension API 1, a configured backend, and working authentication. Keep a private source checkpoint, including existing customizations. Use Node.js 20 or newer.

02

Run guided setup.

Extract the kit outside the Seedly source folder. From the kit directory, run node setup.mjs. The check identifies supported integration files, changed files, and destination conflicts before installation.

03

Build and connect.

Deploy the included required helper from your authoritative backend source before connected edits. Follow QUICKSTART.md with your project’s existing package manager. Build the web app, sign in, and open your existing /location/YOUR_LOCATION_ID address. Verify access, navigation, and your important CRM flows.

Install the interface.
Choose the starting content.

Frontend installation and optional account content are separate. The included original backend helpers are required for connected episode creation, edits, the account store and resource setup. They preserve native account permissions, unrelated custom fields and row history, run the guard on the server, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional. Follow QUICKSTART.md and STARTER_CONTENT.md for the exact integration. The frontend installer does not deploy your backend.

Pick your starting structure.

Starter setup offers Patient episodes, Referral intake, Referral source development, Clinician recruiting. Select individual pipelines and drafts, or use a suitable existing pipeline with the exact stage needed by the chosen draft.

Adapt each workflow.

All nine workflows remain inactive drafts. Review their native triggers, internal tasks, notes, timing, and assignments before publishing in Seedly. Timed waits do not check whether a task is complete or the stage has changed. These examples do not send customer messages.

Explore sample mode.

Explore 24 fictional episodes: 12 admitted, of which 1 has passed day 60 with no next period recorded, 3 are in the recertification window, 3 carry recorded short weeks and 2 have a discharge planned, plus 7 referrals in intake, 2 not admitted and 3 discharged. Seven fictional clinicians with one over the recorded caseload maximum, six referral sources, 215 visit rows with 6 recorded as missed, and 21 orders of which 11 await signature and 4 are overdue at 21 days. Sample edits stay in memory and reset on navigation or reload. Add ?example=1 to the home or custom-view URL. Leave sample mode to return to your real account.

MORE OF THE WORKING DAY

From the first inquiry
to the final handoff.

Editable native forms and document templates give your team a practical starting point.

01 / INTAKE & FOLLOW-UP

Three ready-to-edit forms.

  • Referral source inquiry: name, organization, email and phone, then the type of organization, services of interest, areas served, the best time for a liaison visit and the best way to reach you, all as fixed choices
  • Family callback request: name, email and phone, then who is asking, the days and time for a callback, what to talk about and whether a referral was already sent, all as fixed choices
  • Clinician job interest: name, email and phone, then discipline, areas, hours wanted and years in home health, all as fixed choices, with no license number

Choose forms individually in Setup & resources, then customize and publish them in the native form builder.

02 / WORKING DOCUMENTS

Three reusable templates.

  • Referral acknowledgement
  • Start of care welcome letter
  • Recertification reminder to a physician office

Open each template in Documents and complete it for the actual job or visit.

03 / THE NEXT STEP

Checklists alongside the work.

Record progress and notes in the kit’s operating views. Keep earlier rows by archiving them, and retain the context for the next person.

Forms collect information for staff review. They do not automatically change the kit’s custom records. Repeating setup preserves existing resource edits.

PLEASE READ

A front-desk workspace, not a medical record.

  • This kit is not a HIPAA compliance product and does not make a practice HIPAA compliant. It is not an EHR, EMR or practice management system.
  • It is built for relationship work: recalls, reminders due, follow-up, intake progress and front-desk tasks. Clinical notes, diagnoses, prescriptions, test results, insurance details and other protected health information belong in your clinical system, not here.
  • You install the kit on your own Seedly CRM. DevLaunch does not host, receive or process your patient data. Your practice decides what it records in its CRM and is responsible for its own privacy, security and regulatory obligations, including any agreements with its hosting and software providers.

INSTALLING WITH AN AI AGENT?

Give it the context.
Keep your custom work.

Existing records and unrelated custom source do not require starting over. Modified integration files need a deliberate merge.

Start with the copy-and-paste prompt in INSTALL_WITH_AI.md.
Read AGENT_INSTALL.md for routes, permissions, provider wiring, backend contracts, and compatibility requirements.
Run node setup.mjs check "/path/to/seedly" before modifying files.
Preserve existing extensions, providers, account controls, custom pages, and unrelated data.
Use a reviewed merge for changed integration files; never replace them with clean copies or bypass the installer’s fingerprints.
Deploy the required write helper from the authoritative backend source before connected edits; preserve existing functions and authorization.
Build and verify account access, original CRM modules, new screens, saving, and reload behavior before publishing.

Make the workspace
feel like your team.

Edit apps/web/components/devlaunch-home-health-agency/config.ts to set agency name, descriptor and default pipeline name, then rebuild. The design applies to the entire web installation. Use separate web installations to evaluate different full-interface kits, rather than stacking their installers.

Starter removal, updates, and rollback

Review unused starter additions for removal in Starter setup before removing the frontend. Server checks preserve edited or published workflows and pipelines with jobs or references. The process targets recorded kit additions rather than sweeping account records.

Preserve your local configuration and source edits. Preview frontend removal with node setup.mjs remove "/path/to/seedly" --dry-run. The automatic uninstaller uses a private restoration receipt and refuses to overwrite later edits. Keep that receipt private and out of public hosting or source exports. Removing frontend files does not remove account data or undeploy backend functions.

For an update, follow the documented removal/install process and reapply your preserved changes. A manually merged installation needs its own private change ledger and reviewed source rollback.

What the workspace records

One contact-linked opportunity is one patient episode, from a received referral through admission to discharge or a recorded reason it was not admitted. It holds the patient label of a first name and last initial, a program label, the stage with the date it was reached, the referral, contact, eligibility recorded, scheduled start of care, start of care and current period start dates, a planned discharge, the referral source and physician office names, a coverage area, a visit plan by discipline with nine weekly planned counts, visits as dated rows with a discipline, a clinician and planned, made or missed, orders by category with sent and returned dates, and an editable start of care checklist. The order threshold, the clinicians and the referral sources live in one account store behind a single revision guard.

A period is 60 days from a recorded period start that is the start of care or a whole number of 60-day periods after it. The recertification window is days 56 to 60 inclusive, counted from that start and today’s date. A past week is Short when the visits recorded as made are below the visits planned for any discipline; the current week never is. An order is Overdue when it has been outstanding for more days than the threshold you record, 21 by default. Every boundary is tested. This is skilled home health, not non-medical home care, and Interval records only what the office typed: it is not OASIS, not electronic visit verification, not a scheduling engine, not billing, claims, PDGM or payer processing, not an eligibility check and not an e-signature service, and it sends no messages to patients, families or physician offices. It stores no diagnosis, clinical or visit note, OASIS answer, medication, vital sign, Medicare Beneficiary Identifier, insurance or Social Security number, license number or date of birth, and a server-enforced guard refuses text that looks like one in every note and label, which is help against accidental entry rather than a guarantee. None of the three public forms has a message box, because a form submission never passes through the kit’s guard.

The kit’s original operational screens share the frame with full CRM modules from your own Seedly source. Existing account permissions, feature gates, and configured providers still determine access to those modules.