Senior Healthcare SaaS Developer Needed for HIPAA-Compliant Pharmacy Ordering Marketplace

Less than 30 hrs/week Job Title: Senior Healthcare Platform Developer Needed for HIPAA-Compliant Pharmacy Ordering Marketplace Project Overview We are seeking an experienced healthcare software development team or senior full-stack developer to design and build a secure, HIPAA-compliant ordering platform for licensed medical professionals. The platform will connect approved medical professionals with multiple integrated pharmacy partners offering products such as peptides, hormone therapies, testosterone, wellness medications, and related treatments. Our goal is to create a professional, intuitive, marketplace-style experience—similar to the ease of navigating Amazon—but built specifically for licensed healthcare professionals and compliant medical ordering workflows. This is not intended to be a public consumer marketplace. Access must be restricted to verified medical professionals and authorized staff. Core Platform

Requirements 1. Medical Professional Registration and Verification * Secure registration for physicians, nurse practitioners, physician assistants, clinics, and authorized medical staff * NPI and professional-license verification * Administrative approval before ordering access is granted * Ability to upload licenses and supporting documentation * Role-based permissions for prescribers, clinic employees, pharmacy partners, and platform administrators * Two-factor authentication * Ability to suspend, approve, or restrict individual accounts 2. Individual Clinic and Provider Portals Each approved user or clinic should receive a secure portal that allows them to: * Create and manage their professional profile * Add authorized team members * Enter and securely manage patient information * Submit patient-specific prescription or order information * View available products and pharmacy options * Track pending, processing, shipped, completed, or canceled orders * Review previous orders * Reorder eligible products * Access invoices, receipts, and supporting documents * Communicate securely regarding an order * Receive shipping and order-status notifications 3. Multi-Pharmacy Integration The platform must support multiple pharmacy partners within one centralized ordering system. Required capabilities include: * Separate pharmacy profiles and product catalogs * Products assigned to specific pharmacies * Pharmacy-specific availability, pricing, and fulfillment rules * Secure routing of orders to the appropriate pharmacy * API integration when supported by the pharmacy * Alternative secure workflows when API access is unavailable * Pharmacy-specific order dashboards * Order acceptance, rejection, and status updates * Shipping and tracking integration * Ability to add additional pharmacies in the future without rebuilding the platform Please explain your experience integrating pharmacies, EHR/EMR systems, e-prescribing services, healthcare APIs, fulfillment systems, or similarly regulated vendors. 4. Product Marketplace and Catalog We want the platform to provide an attractive and easy-to-navigate marketplace experience. Products should be organized into categories such as: * Weight management * Recovery and healing * Hormone optimization * Sexual wellness * Performance and body composition * Longevity and wellness * Injectable nutrients * Additional treatment categories The catalog should support: * Product images * Product descriptions * Available strengths and formats * Pharmacy-specific pricing * Educational information * Search and filtering * Frequently ordered items * Featured products * Product availability controls * Prescriber-only warnings and disclosures * Custom pricing based on user, clinic, pharmacy, or membership level The design should feel premium, modern, professional, and easy to use. 5. Patient and Prescription Workflows The platform should support secure patient-specific ordering workflows, including: * Patient demographic information * Relevant medical information required by the fulfilling pharmacy * Prescription details * Dosage and quantity * Prescriber information * Medical-necessity or supporting documentation when required * Electronic signatures and attestations * Consent-form management * Required acknowledgments * Secure document uploads * Order review before submission * Audit history for changes and submissions Because the platform may include testosterone and other controlled or highly regulated medications, applicants must understand that applicable DEA, EPCS, state prescribing, telehealth, and pharmacy requirements may affect the final workflow. The selected developer will need to work alongside our pharmacy partners and healthcare compliance counsel. The developer is not expected to independently provide legal advice, but the system must be capable of implementing the approved compliance requirements. 6. Checkout, Billing, and Payments The platform should include a secure checkout experience with: * Product and order summary * Pharmacy assignment * Shipping information * Taxes and fees, when applicable * Discount or account-specific pricing * Saved payment methods, if permitted * Payment processing * Receipts and invoices * Refund or cancellation workflows * Failed-payment notifications * Clear separation of platform, pharmacy, medication, consultation, and shipping charges when required Applicants should explain their experience working with payment processors that allow healthcare, prescription, pharmacy, or other regulated transactions. Do not assume that a standard consumer payment processor will approve this business model. 7. HIPAA, Security, and Compliance This platform must be designed around HIPAA and healthcare-data security from the beginning. Expected capabilities include: * HIPAA-eligible hosting and infrastructure * Business Associate Agreements where required * Encryption in transit and at rest * Role-based access controls * Multi-factor authentication * Detailed audit logs * Automatic session expiration * Secure backups and disaster recovery * Access and activity monitoring * Secure document storage * Data-retention and deletion policies * Incident-response capabilities * Environment separation for development, testing, and production * No use of live patient information in development or testing * PCI-compliant payment architecture * Security testing before launch Applicants must explain which vendors, hosting providers, APIs, and third-party services would have access to protected health information and whether those vendors support HIPAA requirements and BAAs. 8. Administrative Dashboard Our internal administrative team will need the ability to: * Review and approve professional accounts * Manage clinics and users * Verify licenses and documentation * Add and manage pharmacy partners * Add, edit, and organize products * Set pricing and user-specific pricing rules * Review orders across all pharmacies * View payment and fulfillment statuses * Generate reports * Monitor user activity * Access audit logs * Manage support requests * Publish educational content and announcements * Control permissions without requiring developer assistance 9. Reporting and Analytics The platform should provide reporting for: * Total orders and revenue * Revenue by clinic, provider, pharmacy, and product * Most frequently ordered products * Average order value * Repeat-order activity * Order-processing times * Pharmacy fulfillment performance * Pending and incomplete orders * User activity * Payment status * Commissions or revenue-share calculations, if applicable Reports should be exportable in CSV or Excel format. Design Expectations The platform must be: * Premium and visually appealing * Mobile responsive * Easy for busy medical professionals to navigate * Organized like a modern marketplace * Designed to make product discovery and ordering efficient * Built with a scalable architecture * Easy to expand with additional pharmacies, product categories, and users We will provide brand colors, logos, pharmacy information, initial product categories, and guidance on the desired customer experience. Project Deliverables The selected developer or agency will be responsible for: 1. Discovery and requirements documentation 2. Recommended system architecture and technology stack 3. User-flow diagrams and technical specifications 4. Wireframes and UI/UX designs 5. Clickable prototype for approval 6. Medical-professional portal 7. Pharmacy partner portal 8. Internal administrative dashboard 9. Patient and prescription-information workflows 10. Multi-pharmacy integration framework 11. Product marketplace and checkout 12. Payment integration 13. Order tracking and notifications 14. Security and HIPAA-related technical safeguards 15. Testing and quality assurance 16. Security and vulnerability testing 17. Production deployment 18. Administrative training 19. Technical documentation 20. Post-launch warranty and support 21. Ongoing maintenance proposal We prefer a milestone-based development agreement, beginning with a paid discovery and architecture phase. Required Experience Please apply only if you or your agency has proven experience building at least one of the following: * HIPAA-compliant healthcare platforms * Pharmacy ordering or fulfillment systems * E-prescribing platforms * Telehealth platforms * EHR or EMR integrations * Healthcare marketplaces * Medical-professional portals * Platforms handling protected health information * Multi-vendor or multi-supplier ordering systems General e-commerce experience by itself is not sufficient for this project. Experience working with pharmacy APIs, NPI verification, healthcare identity management, EPCS, controlled-substance workflows, HIPAA-eligible cloud infrastructure, and regulated payment processors is strongly preferred. Information Required in Your Proposal Proposals that do not address all the following items may not be considered: 1. Relevant experience: Describe healthcare, pharmacy, telehealth, e-prescribing, or HIPAA-regulated platforms you have previously built. 2. Examples: Provide links, screenshots, case studies, or demonstrations of comparable platforms. Clearly describe which portions your team completed. 3. Recommended approach: Explain how you would architect a secure platform that can integrate multiple pharmacies and support additional partners in the future. 4. HIPAA and security experience: Describe how you have handled protected health information, access controls, audit logs, encryption, BAAs, backups, and incident response. 5. Pharmacy integrations: Explain your experience integrating pharmacy, EHR, EMR, e-prescribing, fulfillment, shipping, or healthcare APIs. 6. Project timeline: Provide a realistic timeline from discovery through production launch. Break the timeline into major milestones. 7. Total project cost: Provide an estimated all-in development cost, including discovery, design, development, integrations, testing, deployment, training, and post-launch support. Identify any assumptions or items that could change the price. 8. Third-party expenses: List expected expenses that are not included in your development price, including hosting, API fees, identity verification, payment processing, security tools, messaging, e-prescribing services, and other software subscriptions. 9. Ongoing monthly fees: Provide the expected monthly cost to maintain and support the platform after launch. Clearly separate: * Hosting and infrastructure * Software and API subscriptions * Security monitoring * Backups * Routine maintenance * Bug fixes * Version and dependency updates * Technical support * Feature-development hours * Emergency support 10. Support structure: Explain what is included in the monthly maintenance agreement, expected response times, and how urgent issues are handled. 11. Team: Identify who will work on the project, their roles, location, availability, and relevant healthcare experience. 12. Technology stack: Explain the proposed front-end, back-end, database, hosting, integration, and security technologies. 13. Ownership: Confirm that we will own the custom source code, designs, documentation, databases, administrator accounts, and deployment environments after final payment. 14. Availability: State when you can begin and how many hours your team can commit each week. Screening Questions Please answer these questions directly in your application: 1. What is the most comparable HIPAA-regulated platform you have built? 2. Have you built a system involving pharmacies, prescriptions, controlled substances, or patient-specific medical orders? 3. How would you verify that only properly licensed medical professionals can access the ordering system? 4. How would you structure the platform so additional pharmacies can be added efficiently? 5. What HIPAA-eligible hosting environment would you recommend, and why? 6. Which third-party vendors would potentially have access to protected health information? 7. How would you maintain audit logs showing who accessed or changed patient information? 8. What is your estimated project timeline? 9. What is your estimated total project cost? 10. What ongoing monthly service and maintenance fees should we expect? 11. What costs would be paid directly to third-party providers? 12. What post-launch warranty do you provide for bugs? 13. Can you provide references from healthcare clients for whom you completed similar work? Engagement Structure We are open to working with either: * An established healthcare software-development agency * A senior developer with a proven healthcare-development team * A specialized health-tech product studio We are not looking for a basic website, a general Shopify store, or a prebuilt marketplace with superficial HIPAA language added afterward. This is a custom healthcare ordering platform that must be properly architected for security, compliance, scalability, and pharmacy integrations. Please begin your proposal with the words “Healthcare GPO Platform” so we know you reviewed the complete project description.