A certification period board for a skilled home health agency. One row per admitted episode with the current 60-day period drawn as nine weeks of visits planned against visits recorded, the recertification window marked, and every order still waiting on a physician signature beside it. Interval is built for nurses and therapists visiting under physician orders, not for non-medical home care shifts.
One row per admitted episode, most urgent first: a period that ended with no next period recorded, then days 56 to 60, then short weeks, then planned discharges. Each of the nine week cells reads visits recorded as made against visits planned for each discipline, and a past week below plan says Short. The orders awaiting signature sit beside the board, longest outstanding first.
Referrals in intake with the date received, the date contact was made, the date the office recorded eligibility as confirmed and the scheduled start of care, then the outcomes with the days from referral to start of care and a not admitted reason as a category label.
A Monday to Sunday grid with a row per clinician and visit labels of the discipline and the patient’s first name and last initial. Missed visits are written out and struck through. It shows what the office recorded; it does not schedule or verify visits.
Each office’s orders with the category label, the patient label, the sent and returned dates and the days outstanding. Set how many days an order may stay unsigned, and anything past it says Overdue. Order content stays with the office and your clinical system.
Hospitals, physician offices, skilled nursing facilities and ACOs with referrals and admissions counted per calendar month for the last three months, the liaison who owns the relationship and the next touch date.
The roster with SN, PT, OT, ST, MSW and HHA disciplines, the recorded caseload read against the maximum you set, the coverage area and the license expiry as a plain date. No license number is recorded anywhere.
Each desk state counts the episodes behind it and opens them, beside orders awaiting signature, visits made and missed in current periods, referrals in intake and clinicians over their recorded maximum. The ledger carries the same Short, Overdue and Period ended flags as the board.
YOUR PROCESS, YOUR STARTING POINT
Useful structure. Only what you choose.
4 pipelines and 9 workflow drafts. Add the parts that match your work, with a separate sample view for exploring the interface.
01 / FOUR PIPELINES
Choose your starting structure.
Use a ready-made stage sequence or connect drafts to a suitable existing pipeline.
Patient episodes · 8 stages
Referral intake · 7 stages
Referral source development · 7 stages
Clinician recruiting · 7 stages
02 / NINE WORKFLOW DRAFTS
Give the next step a shape.
New referral contact task
Eligibility recorded task
Start of care scheduled note
Start of care admin checklist task
Plan of care signature chase
Recertification reminder task
Discharge planned task
Liaison touch task
Clinician interest follow-up
Native trigger, task, wait, and note nodes provide editable examples. Every draft stays inactive until you review and publish it.
03 / SAMPLE WORKSPACE
Explore before adding records.
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.
No sample customers are inserted into your CRM.
Starter setup checks selected kit additions before removal and preserves edited records and live work.
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.
THE KIT, UNPACKED
Your workspace. Your starting point. Your code to edit.
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.
Certification period board with nine week cells per episode and the orders awaiting signature beside it
Referrals operating view from received to start of care
Visits operating view by clinician and day
Orders operating view by physician office with the recorded threshold
Referral sources operating view with monthly referral and admission counts
Clinicians operating view with recorded caseload against a recorded maximum
Insights operating view of recorded counts only
An account store for the order threshold, clinicians and referral sources behind one revision guard
Three closed-choice native form drafts and three editable letter templates
Editable per-record start of care checklists and preserved row history
Four optional pipeline templates and nine inactive workflow drafts
24 fictional in-memory episodes with 7 clinicians and 21 orders
Guided setup, compatibility report, and private rollback receipt
AI-agent documentation for customized installations
Original editable source, configuration, and tests
Run the guided setup from the extracted kit. Supported integrations can be installed directly; customized integration files get a reviewed merge.
02
Connect the required helper.
Deploy the included helper from your authoritative backend source before connected edits. Build your web app, then choose any optional pipelines and drafts you need.
03
Set up your own team.
Edit agency name, descriptor and default pipeline name. Sign in with your account and verify the workflows and permissions your team uses.
Compatibility and operational details
Seedly CRM 5.8.4 · extension API 1. Node.js 20 or newer. The installer checks supported integration-file versions and does not deploy your web app or backend. 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.
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.
Calling, messaging, signing, payments, and external integrations depend on your Seedly installation, account permissions, plan, and configured providers. Screenshots use sample data and reference imagery. Hosting, installation, and ongoing maintenance are your responsibility.
Checking access…
DEVLAUNCH ALL ACCESS
Every kit. And everything else.
DevLaunch All Access includes every GoSeedly CRM kit, all 195 available today, along with every class, course, and product we release, and private calls with Aaron.
All 195 CRM kits
Every published kit as original editable source, with optional pipelines, workflow drafts, and guided installers. Browse the kits
Every class, course, and product
The full DevLaunch library and software collection, plus each eligible release during your access year, added to your portal as it ships.
Private calls with Aaron
Bring the idea, the offer, or the bottleneck, and leave with a plan you can follow.
DevLaunch All Access
Want more than one kit? All Access covers the whole CRM kit library and the rest of what we make. See everything it includes on the All Access page.
For your own compatible Seedly CRM. Seedly software, hosting and installation services are separate. Each full-interface kit uses its own web installation.
BEFORE YOU MAKE IT YOURS
Good questions. Clear answers.
Is this kit HIPAA compliant?+
No, and it does not claim to be. It is not a HIPAA compliance product, an EHR or a practice management system, and installing it does not make a practice compliant. It is a front-desk and relationship workspace for recalls, reminders, follow-up and intake progress. Keep clinical notes, diagnoses, prescriptions, test results, insurance details and other protected health information in your clinical system. The kit runs on your own Seedly CRM; DevLaunch does not host, receive or process your patient data, and your practice remains responsible for its own privacy, security and regulatory obligations.
How do I receive the kit?+
Purchase securely through Whop. Your original source ZIP and installation documentation are delivered manually to the email used at checkout. This is a one-time purchase of this kit; Seedly software, hosting, and installation services are separate.
Does this include Seedly CRM?+
You obtain and configure Seedly separately. The kit adds original frontend screens, a shared theme, starter definitions, and integration instructions. It does not include Seedly’s codebase, license, hosting, or a separate CRM database.
Is this one connected workspace?+
Interval keeps one deep plum-grey top bar across the kit views and native CRM tools in the same signed-in account, over a light canvas with the period board using the full width of the screen. Contacts, Calendar, Estimates, Documents, and other full modules retain the functionality supplied by your own Seedly installation. Existing authored content and provider screens retain their own layouts.
Can I use it with existing customizations?+
Yes, with a compatibility review. The installer checks the supported integration files. Changed integration files need a reviewed merge; the included AI-agent guide explains how to preserve custom extensions, permissions, providers, and routes.
Do I have to import all the starter content?+
No. Choose individual pipelines and workflow drafts, use a compatible existing pipeline, or install none. Workflows remain inactive until reviewed and published. They use native triggers, internal tasks, optional notes, and timed waits. A wait does not verify task completion or recheck the current stage. The included drafts do not send customer messages.
Can I remove the examples and starter content?+
Sample records stay in memory and never create customers in your CRM. Leave sample mode to return to your account. Starter setup lets you review removal of unused kit additions; server checks retain edited or published workflows and pipelines with live work or references. Removing the frontend does not delete account records.
Can different subaccounts use different kits?+
The current design and branding apply to the whole web installation. Subaccounts still separate data and access. Use a separate web installation for another full-interface kit; running different kit designs by subaccount in one installation requires additional customization.
Selected excerpts from reviews of DevLaunch training, software, and services. Individual customer experiences across DevLaunch.
Your privacy, your choice.
We use essential storage to keep the site working. With your permission, we also use analytics and the Whop Pixel to understand visits and advertising results. Optional analytics stay off until you choose.