Node 22 / NestJS storefront for the AsterMD platform, built on the AsterMD telehealth API: sessions, intake forms and orders. AsterMD is a white-label, API-first telehealth platform.
The storefront is server-rendered and carries a visitor from a product page to a paid, clinically-reviewable order: catalog and cart, a definition-driven intake questionnaire, an optional identity check, checkout against a payment aggregator, post-purchase upsells, and a receipt.
Node 22+ on NestJS 11, EJS templates, Prisma over SQLite, nest-commander for the CLI, and Tailwind v4 for the theme. No JavaScript framework on the client, no queue, no separate application server: one Node process in front of a database, plus a cron table.
It talks to two external systems:
- the AsterMD platform, through the official
@astermd-hq/sdk— product catalog, analytics sessions, teleform (questionnaire) definitions, intake submissions and checkout-funnel events; - a payment aggregator, through
@astermd-hq/vrio-clientor@astermd-hq/checkoutchamp-client, chosen per the synced channel's payment processor — the charge itself, promotions, and the reference order that later upsell charges reuse.
The two are kept apart on purpose. Card data reaches the payment adapter and nothing else. It is never sent to the AsterMD platform and never written to this application's database.
- Product catalog, cart and cross-sells, with several prescriptions allowed in one order
- Intake questionnaire rendered from AsterMD teleform definitions
- Optional identity verification step
- Checkout with an idempotency key (a
UNIQUEconstraint is what prevents a double charge) - Post-purchase upsells and a receipt page
- SEO:
robots.txt, sitemap, structured data, per-route indexing rules - Console commands for catalog sync, reconciliation, pruning and ops reporting
- Real AsterMD and payment integrations behind ports, with Null implementations so tests never touch the network
| Node | >= 22 (see engines in package.json, .nvmrc) |
| npm | any current version |
| Database | SQLite by default (prisma/schema.prisma). Postgres/MySQL are not yet validated. |
npm install
cp .env.example .env # then edit it, see Configuration below
cp config/channel.generated.example.ts config/channel.generated.ts # until theme:sync --apply writes it
npx prisma migrate deploy # creates the SQLite file and applies migrations
npm run build:assets # compiles the Tailwind theme
npm run start:dev # dev server with watch, http://localhost:8080Check it came up:
curl -s localhost:8080/health/Production-style run (builds the app and the assets, then starts it):
npm start # prestart runs `npm run build && npm run build:assets`Two layers. .env holds credentials and per-environment values. config/*.ts holds behaviour, and
it is meant to be read: settings carry doc comments explaining not just what they do but why.
.env.example is the starting point. The ones you will touch first:
| Variable | Purpose |
|---|---|
NODE_ENV |
production, test, or anything else for development. Outside production the whole site is noindex. |
PORT, APP_URL |
listen port and public base URL |
DATABASE_URL |
Prisma connection string (SQLite file by default) |
SESSION_SECRET |
signs the session cookie. Set a real value in every real environment. |
ASTERMD_CLIENT_ID, ASTERMD_CLIENT_SECRET |
AsterMD API credentials, issued to your deployment |
ASTERMD_BASE_HOST, ASTERMD_CHANNEL_ID |
which AsterMD host and sales channel this storefront sells |
AMD_TRACKING_KEY (+ _PREVIOUS) |
affiliate-link payload key, issued to you; leave empty if unused |
PATIENT_PORTAL_URL |
optional "manage your care" links |
GOOGLE_MAPS_API_KEY |
optional: checkout address suggestions come from Google Places when set, from the AsterMD API otherwise; also the receipt map |
EMR_VERIFY_EMAIL, EMR_VERIFY_ADDRESS, VERIFICATION_ENABLED |
optional verification features, all off by default (EMR_VERIFICATION, the older single switch, still sets both checks when neither is given) |
WIRE_LOG |
logs every AsterMD/provider call unredacted. Never enable on a real deployment. |
Real credentials live only in .env, which is gitignored. With the AsterMD credentials blank, the
gateways degrade gracefully (logged errors instead of a crash).
npm run console -- theme:sync --apply regenerates config/products.generated.ts and
config/channel.generated.ts from the AsterMD sales channel. Both are one channel's data and the second holds
payment-provider credentials, so both are gitignored and must never be committed. Sync is a dry
run unless you pass --apply.
npm run start:dev # nest start --watch, http://localhost:8080
npm run build # nest build
npm start # build + assets, then node dist/src/main.js
npm run dev:theme # rebuild CSS/JS on save, for design worknpm run console -- <command>| Command | What it does |
|---|---|
db:migrate |
applies pending Prisma migrations |
theme:sync [--channel <id>] [--apply] |
pulls the channel's catalog and payment config. Dry run without --apply. |
config:validate |
validates the loaded config; exit code 2 on error |
emr:ping / provider:ping |
connectivity checks against the AsterMD API / the payment adapter |
emr:reconcile / provider:reconcile |
reconciliation sweeps |
payment:capture |
settles an order that was authorized rather than charged |
forms:record --teleform=<id> --out=<dir> |
dumps a teleform's raw metadata and definition |
forms:cache-purge |
clears the teleform-definition cache |
cache:clear |
clears the AsterMD bearer-token cache |
media:prune |
removes orphaned synced product images |
abandonment:signals |
abandoned-journey sweep |
db:prune |
retention/log pruning |
ops:status |
operational counts |
npm run db:view # http://localhost:5959/ — read-only browser for every tableA small standalone dev tool, started separately from the app and never a runtime dependency.
npm run typecheck # tsc --noEmit
npm run lint # eslint
npm test # jest — unit + e2e specsNo test reaches the network. NODE_ENV=test turns AsterMD sessions and verification off, so
every AsterMD gateway is Null-bound under the suite.
- Never commit
.envorconfig/channel.generated.ts; both are gitignored. - Set
SESSION_SECRETto a real value outside local development. The built-in fallback is a placeholder. - Never enable
WIRE_LOGon a real deployment. It writes card data, bearer tokens and personal details tostorage/logs/verbatim. - Resume links are permanent.
?amd_session=<uuid>restores a visitor's intake answers (health information) and does not expire. Treatstorage/logs/andabandonment:signalsoutput with the same care as the links themselves. - Identity verification ships disabled. Do not turn it on without first confirming against the provider that a known-good identity comes back valid.
- The shipped legal pages (
/terms/,/privacy/,/telehealth-consent/) are placeholders. Replace the wording before going live.
See docs/OPERATIONS.md for the operator runbook.
config/ per-deployment behaviour config, one .ts file per concern
prisma/ schema.prisma and migrations
src/ application code: core/, domain/, emr/, payment/, funnel/, journey/,
middleware/, routes/, console/, support/
views/ EJS templates (pages/ and partials/)
public/ static files and built assets
build/ asset pipeline and dev tools (Tailwind build, watcher, db viewer)
storage/ gitignored: cache, logs, sessions, SQLite file
test/ Jest unit and e2e specs
docs/ architecture, operations, middleware, journey notes
docs/STACK.md |
the stack, request lifecycle, container and the reasoning behind each choice |
docs/ARCHITECTURE.md |
how the funnel, journey store, catalog and gateways fit together |
docs/MIDDLEWARE.md |
the nine-slot middleware pipeline, slot by slot |
docs/JOURNEY.md |
one customer journey traced end to end |
docs/OPERATIONS.md |
runbook: scheduled jobs and what each report means |
docs/INTEGRATION-NOTES.md |
what the AsterMD API and payment provider actually do, as measured |
docs/SPEC-REFERENCE.md |
resolves the [n.n] rule citations found in the source |
1.0.0 — first release. package.json and the release tag should always agree.
MIT © 2026 CodeClouds™ DBA AsterMD
The AsterMD name and logo are proprietary to AsterMD. The MIT license covers the source code in this repository only and does not grant rights to use the AsterMD brand.
AsterMD is a telehealth platform that helps healthcare brands launch and grow virtual care services. It includes intake builders, patient portals and your choice of providers and pharmacy, with no vendor lock-in. astermd.com · hello@astermd.com