CONTRACT BRIEF – FULL SYSTEM VALIDATION FOR PLATFORM MEDICAL
Budget: $30 – $250 USD
Objective:
Hire a qualified professional to test, validate, and document the entire platform medical , including all features, visual structure, business logic, server configuration, and integrations, based on the full technical scope and the attached business rules document.
1. VISUAL VALIDATION (Front-End Restoration)
Compare restored files (based on the snapshot) with the current live version.
Ensure complete visual fidelity: layout, HTML, CSS, JS, images, components, and responsiveness.
Perform cross-device and cross-browser testing.
2. FUNCTIONAL VALIDATION (Full Platform – Real Scenario)
Perform complete validation using multiple simulated users (admin, patient, professional) for the following features:
Public Streaming (video stability, buffering, real-time chat)
Timed Private Rooms (3, 5, and 7-minute sessions with visible countdown and auto-close)
Stripe Connect Integration (escrow and automatic revenue split)
Mercado Pago Integration (dynamic commission configuration and fallback mode)
Subscription System via Mercado Pago (tiered access control and content restrictions)
Premium Gallery Purchases (payment and revenue split logic)
Token System for Private Room Access
Real-Time Notifications (via Firebase and AWS SNS)
Content Moderation Tools (AWS Rekognition + manual admin tools)
Full Admin Panel Validation (role permissions, campaign management, profile highlighting, asset uploads)
PWA and WebView Compatibility (Flutter for Android/iOS with push and geolocation)
3. BUSINESS LOGIC AND RULE VALIDATION
Review all business rules described in the attached document, including but not limited to:
Plan-based access restrictions (Free vs Premium)
Token requirements for proposals and room access
Revenue split triggers and conditions
Automatic moderation of content (nudity, minors, violence)
Fallback handling for payment systems
Visibility and feature restrictions based on profile upgrades or subscriptions
Escrow behavior and dispute logic
Admin interventions and real-time alert responses
4. SERVER CONFIGURATION REVIEW (AWS)
Review current AWS server configuration and deployment settings
Check performance optimization: EC2 instance types, load balancing, scalability
Validate security practices: access keys, firewalls, SSH access, PEM key control
Confirm backup routines, monitoring, and logging are properly set up
Validate correct integration of services (SNS, Rekognition, S3, etc.)
Provide a clear report on any misconfiguration or security risk
5. TESTING METHODOLOGY (MANDATORY)
All tests must simulate real-world usage scenarios with distinct user roles.
Each functionality must be recorded via screen capture with voice narration, explaining the test steps and outcomes.
Testing must cover desktop, mobile, and PWA installations.
6. REQUIRED DELIVERABLES
Full Validation Report:
Checklist of approved features
List of inconsistencies or issues (with proof)
Validation or rejection of business rules
Findings from AWS server configuration review
Screen recordings with voice narration for each tested item
Suggestions for fixes or optimizations (optional but recommended)
7. FINAL NOTES
The professional must not alter any source code, only test and report.
Technical materials and rule documentation will be provided upon start.
Delivery will be evaluated based on completeness, clarity, and objective evidence.
Hire a qualified professional to test, validate, and document the entire platform medical , including all features, visual structure, business logic, server configuration, and integrations, based on the full technical scope and the attached business rules document.
1. VISUAL VALIDATION (Front-End Restoration)
Compare restored files (based on the snapshot) with the current live version.
Ensure complete visual fidelity: layout, HTML, CSS, JS, images, components, and responsiveness.
Perform cross-device and cross-browser testing.
2. FUNCTIONAL VALIDATION (Full Platform – Real Scenario)
Perform complete validation using multiple simulated users (admin, patient, professional) for the following features:
Public Streaming (video stability, buffering, real-time chat)
Timed Private Rooms (3, 5, and 7-minute sessions with visible countdown and auto-close)
Stripe Connect Integration (escrow and automatic revenue split)
Mercado Pago Integration (dynamic commission configuration and fallback mode)
Subscription System via Mercado Pago (tiered access control and content restrictions)
Premium Gallery Purchases (payment and revenue split logic)
Token System for Private Room Access
Real-Time Notifications (via Firebase and AWS SNS)
Content Moderation Tools (AWS Rekognition + manual admin tools)
Full Admin Panel Validation (role permissions, campaign management, profile highlighting, asset uploads)
PWA and WebView Compatibility (Flutter for Android/iOS with push and geolocation)
3. BUSINESS LOGIC AND RULE VALIDATION
Review all business rules described in the attached document, including but not limited to:
Plan-based access restrictions (Free vs Premium)
Token requirements for proposals and room access
Revenue split triggers and conditions
Automatic moderation of content (nudity, minors, violence)
Fallback handling for payment systems
Visibility and feature restrictions based on profile upgrades or subscriptions
Escrow behavior and dispute logic
Admin interventions and real-time alert responses
4. SERVER CONFIGURATION REVIEW (AWS)
Review current AWS server configuration and deployment settings
Check performance optimization: EC2 instance types, load balancing, scalability
Validate security practices: access keys, firewalls, SSH access, PEM key control
Confirm backup routines, monitoring, and logging are properly set up
Validate correct integration of services (SNS, Rekognition, S3, etc.)
Provide a clear report on any misconfiguration or security risk
5. TESTING METHODOLOGY (MANDATORY)
All tests must simulate real-world usage scenarios with distinct user roles.
Each functionality must be recorded via screen capture with voice narration, explaining the test steps and outcomes.
Testing must cover desktop, mobile, and PWA installations.
6. REQUIRED DELIVERABLES
Full Validation Report:
Checklist of approved features
List of inconsistencies or issues (with proof)
Validation or rejection of business rules
Findings from AWS server configuration review
Screen recordings with voice narration for each tested item
Suggestions for fixes or optimizations (optional but recommended)
7. FINAL NOTES
The professional must not alter any source code, only test and report.
Technical materials and rule documentation will be provided upon start.
Delivery will be evaluated based on completeness, clarity, and objective evidence.