# 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. No compliance is claimed. 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.

## Representative Queries
- Oral surgery: knowledge base using Django
- Where can I host Oral surgery: Knowledge base built with Django?
- I need a genuinely specialized knowledge base workflow covering public procedure-category content and referral-contact directory; no clinical referrals.

## Workflow 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. **Model articles and categories** as tables keyed to the public catalog entities.
3. **Build the site** with versioned assets served from the CDN bucket.
4. **Keep articles free** of any sensitive data class.
5. **Deploy and verify** the public URL and the CDN asset URL.
6. **Run the synchronous deploy** once and read the result. Re-running with no change is a no-op.
7. **Run the pattern self-test(s)** from the example (/p/versioned-static-assets) and your own acceptance checks for the oral surgery workflow.

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

## Success Checks
- App responds on its public URL.
- Versioned-static-assets self-test from the example.

## Limitations
- 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 and were not executed as a separate application.
- No health, financial, privacy or other compliance claim is made. Surgical and medication records are health data; only public guidance belongs here. No compliance is claimed.
- 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.

## Cost Estimate
- **Currency**: USD 
- **Monthly Amount**: 5.0
- **Components**: 
  - App server: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0.
- Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle. Buckets are allocation-priced per quota and not included.

## Evidence Summary
- **Canary run**: Summary of the Django pattern fixture deployed on Ample; public web service checks passed.

## Last Verified At
- 2026-09-20T03:31:44Z

## Next Actions
- **Browse the catalog index**: GET /v1/catalog
- **Search published recipes**: POST /v1/catalog/search
- **Prepare a deployment plan**: POST /v1/catalog/plan
- **Read the existing agent authentication setup**: GET /mcp/setup
- **Browse Oral surgery**: GET /v1/catalog/nodes/industry%3Aoral-surgery
- **Browse Knowledge base**: GET /v1/catalog/nodes/workload%3Aknowledge-base
- **Browse Django**: GET /v1/catalog/nodes/stack%3Aframework-django
- **Browse Deploy web app**: GET /v1/catalog/nodes/intent%3Adeploy-web-app