General dentistry: knowledge base using Django

Summary

A knowledge base blueprint for general dentistry built with Django on Ample. Domain schema: services (code, name, description, duration_minutes, price_from): the treatments a practice offers; locations (name, address, phone, opening_hours, accessibility_notes): each practice location; dentists (name, registration_number, specialties, location_id): the clinicians listed publicly; insurance_plans (name, accepted_at_location_id): plans accepted per location; asset_versions (version, cdn_key, published_at): versioned assets served from the CDN bucket. Public information: service catalog with prices from, locations, hours and parking, clinician profiles and registrations, accepted insurance plans. Kept out of scope until handling is reviewed: patient identity and contact details, clinical records, x-rays and treatment notes, appointment history tied to a person. Patient data is health data. Keep it out of these workflows until handling requirements (for example HIPAA in the United States) have been reviewed; nothing here establishes compliance. Technical basis verified on Django: a versioned, immutable-cached asset uploaded to a published bucket and served from the CDN URL alongside the app's own public HTTPS URL.

Infrastructure requirements

• Compute: verified (Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.)
• CDN: verified (The CDN host serves objects from published buckets. It does not front app compute and is not a cache or key-value store.)

Prerequisites

• A Django project (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 template)
• Bucket credentials from ample bucket create passed as encrypted S3_* environment variables and a published bucket for public assets (CDN_*)
• A review of which general dentistry data classes may be handled at all; this blueprint models public information only

Exact tested configuration

• template: python-3.12
• runtime: python
• size: s-1vcpu-1gb
• install: python3 -m pip install --target .ample/python -r requirements.txt
• start: PYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py

Steps

1. Model the general dentistry domain. Create the tables services, locations, dentists, insurance_plans, asset_versions. The treatments a practice offers lives in services; keep the sensitive classes (patient identity and contact details, clinical records, x-rays and treatment notes, appointment history tied to a person) out of this schema.
2. Workflow step 1. Model articles and categories as tables keyed to the public catalog entities
3. Workflow step 2. Build the site with versioned assets served from the CDN bucket
4. Workflow step 3. Keep articles free of any sensitive data class
5. Workflow step 4. Deploy and verify the public URL and the CDN asset URL
6. 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 --start "python3 run.py" --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=... --env CDN_PUBLIC_URL=...

7. Verify. Run the pattern self-test(s) from the example (/p/versioned-static-assets) and your own acceptance checks for the general dentistry workflow.

   ample logs <deployment_id> --kind build

Tested examples

• Django pattern fixture: Verified public web service basis for this blueprint.

Success checks

• app responds on its public URL (/ on the live URL, expect ample canary django patterns)
• versioned-static-assets self-test from the example (/p/versioned-static-assets on the live URL, expect see the pattern fixture checks)

Limitations

• The technical basis (public web service on Django) was verified with the pattern fixture; the general dentistry schema and workflow are an original design for this blueprint and were not executed as a separate application.
• No health, financial, privacy or other compliance claim is made. Patient data is health data. Keep it out of these workflows until handling requirements (for example HIPAA in the United States) have been reviewed; nothing here establishes compliance.
• Public content and synthetic examples only until actual data-handling requirements have been reviewed.
• Verified on the python-3.12 template at s-1vcpu-1gb; region, request-duration limits and other sizes are unknown or unverified.
• PutObject and GetObject with path-style addressing are verified; other S3 operations and CDN cache rules are not.

Cost estimate

Estimated 5.00 USD per month (size prices from pricing.toml at build revision a1b8c38919e59cd035ebabaced73cf84ece24371).

• app server x1 s-1vcpu-1gb: 5.00 USD

Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

Verification evidence

• canary_run on 2026-09-20T03:31:44Z at revision 03b6402b1b3e19178985f08ea4033804521d85d4-dirty (CLI b75e104): Django pattern fixture deployed on Ample (pip install into .ample/python from requirements.txt, then waitress serving project.wsgi from run.py reading PORT on the python-3.12 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 General dentistry schema and workflow below build on that verified basis and were not separately executed. (expires 2027-03-19T03:31:44Z)

Execution binding

MCP tool ample_deploy (registry mcp:ample_deploy), schema hash 876465fce906da0c observed 2026-09-21T03:19:59.461917+00:00 at revision 49962bcade4f, binding state current, required scopes: servers:write, buckets:read.