Oral surgery: knowledge base using Next.js · Ample Computer
Oral surgery: knowledge base using Next.js
A knowledge base blueprint for oral surgery built with Next.js on Ample. Domain schema: procedures (code, name, description, anesthesia_options, recovery_days): extractions, implants and corrective surgery; pre_op_instructions (procedure_id, instructions, fasting_rules): public preparation guidance; post_op_instructions (procedure_id, instructions, warning_signs): public recovery guidance; locations (name, address, phone, opening_hours, emergency_line): surgery locations; asset_versions (version, cdn_key, published_at): versioned assets served from the CDN bucket. Public information: procedure catalog with recovery expectations, pre- and post-operative instructions, emergency contact per location. Kept out of scope until handling is reviewed: surgical records and consent forms, medication lists, insurance pre-authorizations. Surgical and medication records are health data; only public guidance belongs here. Technical basis verified on Next.js: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL.
What it runs on
Computeverified
Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.CDNverified
A published bucket's objects are served from its public URL; set Cache-Control when uploading to control caching. App responses are served by the app.
You need
- A Next.js project (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template)
- Bucket credentials from
ample bucket createpassed as encrypted S3_* environment variables and a published bucket for public assets (CDN_*) - A review of which oral surgery data classes may be handled at all; this blueprint models public information only
Exact tested configuration
build
npm run build --if-present
install
npm install
runtime
node
sizes-1vcpu-1gb
start
npm run start
template
node-22
Steps
Model the oral surgery domain. Create the tables procedures, pre_op_instructions, post_op_instructions, locations, asset_versions. Extractions, implants and corrective surgery lives in procedures; keep the sensitive classes (surgical records and consent forms, medication lists, insurance pre-authorizations) out of this schema.
Workflow step 1. Model articles and categories as tables keyed to the public catalog entities.
Workflow step 2. Build the site with versioned assets served from the CDN bucket.
Workflow step 3. Keep articles free of any sensitive data class.
Workflow step 4. Deploy and verify the public URL and the CDN asset URL.
Deploy. Run the synchronous deploy once and read the result. Re-running with no change is a no-op.
$ ample deploy . --name <app-name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...
- Verify. Run the pattern self-test(s) from the example (/p/versioned-static-assets) and your own acceptance checks for the oral surgery workflow.
$ ample logs <deployment_id> --kind build
How it was checked
✓app responds on its public URL· http get/ → “ample canary next js patterns”
✓versioned-static-assets self-test from the example· http get/p/versioned-static-assets → “see the pattern fixture checks”
Evidence
- November 5, 2026 · canary run
Next.js pattern fixture deployed on Ample (next build then next start -H 0.0.0.0 -p $PORT on the node-22 template); the public web service checks passed: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL. The blueprint's Oral surgery schema and workflow below build on that verified basis.
Tested examples
- Next.js pattern fixture. Verified public web service basis for this blueprint.
What it doesn’t cover
- The technical basis (public web service on Next.js) was verified with the pattern fixture; the oral surgery schema and workflow are an original design for this blueprint, built on that basis.
- Surgical and medication records are health data; only public guidance belongs here.
- Verified on the node-22 template at s-1vcpu-1gb.
- Buckets speak the standard S3 API (PutObject and GetObject with path-style addressing are checked by the fixture);
ample bucket upload-urlreturns presigned upload URLs.