Skip to main content

Writing schemas with AI

warning

RehabAlpha is still under active development. It is not yet HIPAA compliant and should only be used with dummy data.

AI tools such as ChatGPT, Gemini, and Claude can be very effective for drafting RehabAlpha schemas.

In many cases, using AI is the fastest way to go from a vague idea like:

  • “I need a PT evaluation template”
  • “I want a falls section”
  • “I need a Medicare-focused SNF template”

to a usable first draft.

Example prompt​

Here is a simple starting prompt:

Review the documentation for RehabAlpha schemas at the following URLs:

1. https://docs.rehabalpha.com/guides/schemas/
2. https://docs.rehabalpha.com/guides/schemas/writing-your-own-schema


TASK:

Create a RehabAlpha evaluation schema for outpatient physical therapy. The clinician needs to document chief complaint, history, pain, knee range of motion, gait, assessment, and plan. Keep it clean and beginner-friendly.


REQUIREMENTS:

- Prevent broken references
- Prevent duplicate or inconsistent naming
- Prevent overcomplicated conditional logic
- Prefer reusable options nodes
- Prefer structured option values
- Keep the schema beginner-friendly
- Avoid deeply nested conditionals
- Keep the template focused and not overly long
- Do not use inline child objects unless necessary
- Optimize for readability over cleverness
- Use clear IDs with consistent naming
- Keep node IDs 100 characters or fewer and use only letters, numbers, underscores, and dashes
- Keep labels, tooltips, descriptions, and placeholders 256 characters or fewer
- Keep text node values 1024 characters or fewer
- Keep option labels and option values 256 characters or fewer
- Keep each options node to 256 items or fewer
- Keep the total schema under 500,000 characters
- Keep each template under 1,028 total reachable nodes and under 1,028 input nodes
- Keep nesting depth under 16 levels, and prefer much shallower nesting when possible
- Knee ROM should include right and left flexion and extension as number inputs
- Include a yes/no pain question
- If pain is present, show pain location and pain level
- Use only supported RehabAlpha node types and properties
- Use only these special context variables in conditions: *disciplineId, *placeOfServiceId, *templateType, and *payorTypes
- Use *disciplineId, not *discipline; valid values are OT, PT, and SLP
- Valid *placeOfServiceId values are POS codes: 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 31, 32, 33, 34, 41, 42, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 60, 61, 62, 65, 66, 71, 72, 81, and 99
- Valid *templateType values are case, discharge, evaluation, progressReport, recertification, and treatment
- *payorTypes is an array; use includes or doesNotInclude with these values: Commercial Insurance, Managed Care Part A, Managed Care Part B, Medicaid, Medicare Part A, Medicare Part B, Private Pay, and Workers' Compensation
- Match all special variable values exactly, including capitalization and spaces


OUTPUT:

Return only the schema as a block of code in JSON5 format with no explanation.
Tip

Use the most powerful, longest thinking AI model you can get your hands on.

Try it​

Copy the example prompts above into your preferred AI tool and see what it produces.