Clinical Study WordPress Integration with Azure
Budget: $750 – $1,500 USD
WordPress Feature Development – Clinical Study Interest Form + Azure Service Bus Integration
Project Overview
We operate a large clinical research site network using WordPress to display active clinical studies across multiple physical locations (“sites”). We need a custom WordPress feature that allows an end user to:
1. View a unified list of studies (filterable by physical location/site).
2. Select one or more studies they are interested in.
3. Submit a single contact form with their personal information.
4. Have the form submission sent to our Azure Service Bus Queue as a structured JSON payload.
This feature will be added to our existing WordPress site.
⸻
Required Deliverables
1. Study Selection Interface
• Pull existing study data from our current WordPress structure.
• Display studies grouped by location (or allow filtering/search).
• Allow users to select multiple studies (checkbox UI).
• Ensure the selected studies flow into the final submission payload.
2. Contact Form
• Custom form fields (we will provide final list), likely including:
• First name
• Last name
• Email
• Phone
• Zip code
• Additional questions (e.g., conditions, referral source)
• Validate inputs on frontend and backend.
You may use:
• A custom plugin
• A theme extension
• Or a block-based solution (Gutenberg block)
(But no page builder dependencies like Elementor.)
3. Azure Service Bus Queue Integration
• On submit, the system must send the form data AND selected study IDs/names to Azure Service Bus Queue.
• Use Azure authentication best practices (we can provide:
• queue connection string
• SAS token
• or we can generate a dedicated access policy
• Payload must be sent as JSON with a defined schema (we will provide sample structure).
• Must gracefully handle errors and log failures.
4. Admin-Configurable Settings
Create a small WordPress admin menu or settings page for:
• Azure Service Bus connection details
• Queue name
• Optional logging toggle
• Test connection button (preferred but optional)
5. Logging
• Log successful and failed submissions.
• Simple log viewer inside WordPress OR write to wp-content logs.
6. Security Requirements
• Validate all inputs server-side.
• Sanitize form fields.
• Do not expose Azure keys to the browser.
• Use nonce and WordPress-native security functions.
⸻
Technical Environment
• WordPress (latest version)
• Hosted in Azure
• PHP 8.x
• Uses custom post types for clinical studies
• Azure Service Bus is already in use across our organization
⸻
Preferred Developer Skills
• Experience building custom WordPress plugins
• Strong PHP, JS, and WordPress REST/API skills
• Demonstrated experience integrating external systems (Azure preferred)
• Understanding of secure form submission patterns
• Familiarity with Azure Service Bus (big plus)
⸻
What We Will Provide
• Sample JSON payload schema
• Azure Service Bus queue name + credentials
• Access to staging environment
• Study structure details (custom post type, fields, taxonomy)
⸻
Success Criteria
• Feature works seamlessly on staging and production
• Fast and responsive UI
• Accurate data transmission to our Azure queue
• Secure and maintainable code
• Clean admin controls for configuration and troubleshooting
Project Overview
We operate a large clinical research site network using WordPress to display active clinical studies across multiple physical locations (“sites”). We need a custom WordPress feature that allows an end user to:
1. View a unified list of studies (filterable by physical location/site).
2. Select one or more studies they are interested in.
3. Submit a single contact form with their personal information.
4. Have the form submission sent to our Azure Service Bus Queue as a structured JSON payload.
This feature will be added to our existing WordPress site.
⸻
Required Deliverables
1. Study Selection Interface
• Pull existing study data from our current WordPress structure.
• Display studies grouped by location (or allow filtering/search).
• Allow users to select multiple studies (checkbox UI).
• Ensure the selected studies flow into the final submission payload.
2. Contact Form
• Custom form fields (we will provide final list), likely including:
• First name
• Last name
• Phone
• Zip code
• Additional questions (e.g., conditions, referral source)
• Validate inputs on frontend and backend.
You may use:
• A custom plugin
• A theme extension
• Or a block-based solution (Gutenberg block)
(But no page builder dependencies like Elementor.)
3. Azure Service Bus Queue Integration
• On submit, the system must send the form data AND selected study IDs/names to Azure Service Bus Queue.
• Use Azure authentication best practices (we can provide:
• queue connection string
• SAS token
• or we can generate a dedicated access policy
• Payload must be sent as JSON with a defined schema (we will provide sample structure).
• Must gracefully handle errors and log failures.
4. Admin-Configurable Settings
Create a small WordPress admin menu or settings page for:
• Azure Service Bus connection details
• Queue name
• Optional logging toggle
• Test connection button (preferred but optional)
5. Logging
• Log successful and failed submissions.
• Simple log viewer inside WordPress OR write to wp-content logs.
6. Security Requirements
• Validate all inputs server-side.
• Sanitize form fields.
• Do not expose Azure keys to the browser.
• Use nonce and WordPress-native security functions.
⸻
Technical Environment
• WordPress (latest version)
• Hosted in Azure
• PHP 8.x
• Uses custom post types for clinical studies
• Azure Service Bus is already in use across our organization
⸻
Preferred Developer Skills
• Experience building custom WordPress plugins
• Strong PHP, JS, and WordPress REST/API skills
• Demonstrated experience integrating external systems (Azure preferred)
• Understanding of secure form submission patterns
• Familiarity with Azure Service Bus (big plus)
⸻
What We Will Provide
• Sample JSON payload schema
• Azure Service Bus queue name + credentials
• Access to staging environment
• Study structure details (custom post type, fields, taxonomy)
⸻
Success Criteria
• Feature works seamlessly on staging and production
• Fast and responsive UI
• Accurate data transmission to our Azure queue
• Secure and maintainable code
• Clean admin controls for configuration and troubleshooting