Skip to main content

Understanding Specode

Think of the Specode AI as a highly skilled developer who:

Component Expertise

Knows all the healthcare components in the foundation

Healthcare Knowledge

Understands healthcare regulations and best practices

Custom Development

Can build features based on your descriptions

Clear Direction

Needs clear direction to deliver exactly what you want

Core Principles for Effective Prompts

Be Specific, Not Vague

I need to add a preferred pharmacy field to the intake form. It should include pharmacy name, address, and phone number so providers know where to send prescriptions.

Describe User Journeys, Not Technical Implementation

When patients cancel an appointment, they should select a reason from a dropdown.
 If they choose "other", show a text box for details. 
 Then send this information as a notification to the provider.

Build Incrementally, Not All at Once

I want to implement a "View Availability" button that patients can view.
First create the button, located right above the "Book" button on the provider card. 
It will be non-functional for now.
Follow Up Prompts
Now let's make the button functional. When the user click's on "View Availability", open a new modal.
Follow Up Prompts
In this new modal, add the calendar ui component. Above it, include the title text "Select a date".
Then continue to iterate incrementally until you achieve your desired functionality.

Include Context and Requirements

Always specify:
Who will use this feature (patients, doctors, staff, administrators)
Specific fields or data that need to be collected or displayed
Any specific healthcare compliance requirements beyond basics
How this feature connects with other parts of your system

Effective Request Patterns

Creating New Features

Template:
I need a [feature type] that allows [user type] to [action]. It should [specific requirements] and [integration needs].
Example:
I need a no-show fee waiver request form that allows patients to explain why they missed
their appointment. It should include:
- A dropdown with common reasons (emergency, transportation issues, illness, work conflict, other)
- A required text field for detailed explanation (minimum 50 characters)
- The patient's contact information pre-filled from their profile
- A checkbox to acknowledge the fee policy
- Submit button that routes the request to the patient's primary provider for approval
- The provider should receive an in-app notification with approve/deny options

Modifying Existing Features

Template:
Can you modify the [existing feature] to [new behavior]? Currently it [current behavior], but I need it to [desired behavior].
Example:
Can you modify the patient intake form to include a visual allergy severity scale?
Currently it just has a text field for allergies, but I need it to:
- Display a 1-5 severity scale with visual indicators (1=mild to 5=severe/life-threatening)
- Use color coding: green (1-2), yellow (3), orange (4), red (5)
- Include icons for common allergens (medications, foods, environmental, latex)
- Allow multiple allergies with different severity levels
- Show a warning banner if any allergy is marked as severe (4-5)
- Make the allergy section required if the patient indicates they have allergies

Fixing Issues

Template:
The [feature] is [problem description]. When [steps to reproduce], 
it [what happens]. It should [expected behavior].
Example:
The provider notes are not saving properly. 
When I type notes during a video call and click save, the notes disappear. 
It should save them to the patient's record and show a confirmation.

What Specode Handles Automatically

You don’t need to specify:

Technical Implementation

Databases, APIs, server configuration

Basic Security

Encryption, secure connections, authentication

Standard Compliance

Basic HIPAA requirements and healthcare standards

Responsive Design

Mobile optimization and cross-device compatibility
Ready to start building? Try your first prompt with Specode, or continue to Theming & Design Changes to learn about visual customization.
I