← Back to writing samples
Agile Requirements
Portfolio sample. Demonstrates software requirement authoring, user story decomposition, and Behavior-Driven Development (BDD / Gherkin) acceptance criteria for an enterprise telehealth platform ('Meridian Health').

Asynchronous Care Platform: Visit Cadence & Clinical Compliance Specifications

Specification Scope: This document details functional requirements for the core clinical engine governing automated visit modality switching (synchronous vs. asynchronous), state-specific medication rule enforcement, audit key rotation, and automated Prior Authorization (PA) filing.

1. Epic Overview

The platform manages clinical visit cadences across complex longitudinal treatment plans, dynamically alternating visit types based on dosing stabilization and regulatory jurisdictions.

2. Feature Specifications & User Stories

Feature: Automated Visit Modality Transition Engine

AS A: Patient enrolled in active medical weight management
I WANT: My monthly check-in to alternate between asynchronous questionnaires and synchronous video consultations
SO THAT: My provider can monitor side effects while minimizing unnecessary clinical office visits.

Scenario: Active titration visit scheduling
  GIVEN a patient is in active dose titration (Steady_State_Flag = False)
  AND the last completed visit was "Synchronous_Video" at Day 0
  WHEN the 30-day follow-up encounter is triggered
  THEN the system generates an "Asynchronous_Clinical_Intake" work item
  AND dispatches a reminder email to the patient with the questionnaire link.

Scenario: Transition to steady-state maintenance
  GIVEN a provider marks a patient's prescription as "Steady_State_Achieved"
  WHEN the subsequent visit schedule is calculated
  THEN the system updates the visit frequency from 30-day alternation to 90-day Synchronous visits
  AND logs the cadence update in the patient audit ledger.

Feature: State-Specific Prescribing & Key Rotation Audit Log

AS A: Compliance Officer
I WANT: State-level prescribing restriction changes to generate immutable audit entries
SO THAT: The platform maintains 100% adherence to state medical board statutory guidelines.

Scenario: Key rotation audit logging
  GIVEN an administrator updates medication prescribing logic tables
  WHEN the new policy key is committed to the database
  THEN the system creates an immutable audit record capturing:
    | Field Name    | Value Description                           |
    | Old_Key_ID    | Pre-change cryptographic version hash       |
    | New_Key_ID    | Post-change cryptographic version hash      |
    | Rotation_Date | ISO 8601 UTC timestamp                      |
    | Vendor_ID     | Integrated pharmacy partner identifier      |
    | Rotated_By    | Authenticated Administrator Profile ID      |