# Oral surgery: knowledge base using Django

A knowledge base blueprint for oral surgery built with Django 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 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.

## What it runs on

- [Computeverified](/content/discover/primitive/compute/index.html)  
  Apps run in isolated x86_64 Firecracker microVMs; sizes are the priced VM sizes.

- [CDNverified](/content/discover/primitive/cdn/index.html)  
  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 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 oral surgery data classes may be handled at all; this blueprint models public information only

## Exact tested configuration

`installpython3 -m pip install --target .ample/python -r requirements.txt`

`runtimepython`

`sizes-1vcpu-1gb`

`startPYTHONPATH=.ample/python:${PYTHONPATH:-} python3 run.py`

`templatepython-3.12`

## Steps

1. **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.

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.

```shell
$ 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 oral surgery workflow.

```shell
$ ample logs <deployment_id> --kind build
```

## How it was checked

✓app responds on its public URL· http get/ → “ample canary django patterns”  
✓versioned-static-assets self-test from the example· http get/p/versioned-static-assets → “see the pattern fixture checks”

## Evidence

1. November 6, 2026 · canary run  
   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 Oral surgery schema and workflow below build on that verified basis.

## Tested examples

- **Django pattern fixture.** Verified public web service basis for this blueprint.

## What it doesn’t cover

- The technical basis (public web service on Django) 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 python-3.12 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-url` returns presigned upload URLs.
