Oral surgery: campaign site using Laravel

Overview

A campaign site blueprint for oral surgery built with Laravel on Ample. Domain schema includes:

• procedures:

  • code
  • name
  • description
  • anesthesia_options
  • recovery_days
    Procedures include extractions, implants, and corrective surgery.

• pre_op_instructions:

  • procedure_id
  • instructions
  • fasting_rules
    Guidance for public preparation.

• post_op_instructions:

  • procedure_id
  • instructions
  • warning_signs
    Guidance for public recovery.

• locations:

  • name
  • address
  • phone
  • opening_hours
  • emergency_line
    Information about surgery locations.

• asset_versions:

  • version
  • cdn_key
  • published_at
    Versioned assets served from the CDN bucket.

Publicly available information includes:

• Procedure catalog with recovery expectations.
• Pre- and post-operative instructions.
• Emergency contact per location.

Key Considerations

• Kept Out of Scope: Surgical records and consent forms, medication lists, insurance pre-authorizations.
• Technical Basis Verified: Operates on Laravel with versioned, immutable-cached assets uploaded to a published bucket.
• Compliance: No compliance claims made; only public guidance is provided.

Representative Queries

• "Oral surgery: campaign site using Laravel"
• "Where can I host Oral surgery: Campaign site built with Laravel?"
• "I need a genuinely specialized campaign site workflow covering public procedure-category content and referral-contact directory; no clinical referrals."

Resource and Infrastructure Requirements

Requirements

• Primitive: Compute, CDN

Infrastructure Details

1. Compute
   • Runs in isolated x86_64 Firecracker microVMs. Sizes are the priced VM sizes.
2. CDN
   • Serves objects from published buckets without caching.

Workflow Steps

1. Model the oral surgery domain:
   • Create tables: procedures, pre_op_instructions, post_op_instructions, locations, asset_versions.
2. Workflow Step 1:
   • Model the campaign's offers and locations as tables with start and end dates.
3. Workflow Step 2:
   • Build the site and publish versioned static assets to the CDN bucket.
4. Workflow Step 3:
   • Collect no personal data on the site; hand off to an authorized system.
5. Workflow Step 4:
   • Deploy, verify the public URL and the CDN asset URL, and retire the campaign by end date.
6. Deploy:
   • Command to run first deployment: ample deploy . --name --public --env S3_ENDPOINT=... --env S3_REGION=...
7. Verify:
   • Run self-test checks for the workflow.

Examples

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

Success Checks

1. App responds on its public URL.
2. Versioned-static-assets self-test from the example.

Limitations

• Compliance and verification limits outlined without claims.

Cost Estimate

• Monthly Amount: $5.00
  Basis: Size prices from pricing.

Evidence Summary

• Deployment details and checks passed on public web service.

Documentation Links

• HTML Format
• Markdown Format
• JSON Format