1mg-style Health Marketplace — Custom-Built for Your Market

A prescription upload, a test booking and a consultation need three different decisions

A caregiver orders medicines for a parent, books a home collection and asks for a consultation in the same session. The prescription image is unclear, the laboratory cannot cover the address and the consultation payment succeeds without a confirmed slot. One green order badge hides three unresolved responsibilities. A useful health marketplace shows which provider accepted each request, whose information is attached and which qualified person must make the next decision.

A 1mg-style health marketplace connects medicine discovery, pharmacy review, diagnostic bookings and consultation routing under an independently branded product. It is not access to Tata 1mg’s provider network, certifications, clinical team or proprietary systems. Buyers need defined operating authority and service boundaries before engineering. This page describes coordination software and buyer acceptance questions, not medical advice, permission to dispense medicines or a guarantee of clinical outcomes.

Choose the operating model before combining the catalog

An owned pharmacy channel and a marketplace of independent pharmacies have different inventory, invoicing and support responsibilities. Adding laboratories introduces collection capacity and report release; consultations introduce professional availability and clinical records. Decide which organization supplies each service, accepts the patient request and answers complaints. A shared account can simplify navigation, but it must not imply that the platform operator performs every professional service.

Compare a focused Netmeds-style pharmacy channel when dispensing and medicine fulfillment are the main business. Keep diagnostics and consultations out of the first release if their provider arrangements are not ready. Your proposal should list supported services, exclusions, required provider contracts and the evidence needed before public availability. A large category menu is not a substitute for an operable network.

Keep patient identity separate from the person paying

The account holder may be ordering for a parent, child or another person. Establish the patient identity and the authority to act for them without assuming that payment gives access to health records. Capture the necessary consent or authorization for the intended market and distinguish patient communication from payer receipts. An old saved profile should not automatically authorize a newly added caregiver to read prescriptions or laboratory reports.

At every provider handoff, carry an agreed patient identifier and enough information to resolve a mismatch. Two people with the same name cannot share a report folder. Record who supplied information, when it was changed and which request used that version. Support should be able to investigate a failed identity match without downloading the entire health history. Rehearse revoked caregiver access and a request associated with the wrong family member.

Make prescription review an accountable professional action

An uploaded document can be incomplete, unreadable, expired under applicable rules or unrelated to the selected items. Store the original submission and its provenance, then route it to the authorized pharmacy review process. Distinguish awaiting review, clarification requested, rejected and approved for specified items. Optical extraction can assist administrative entry but must not turn recognized text into clinical approval or invent a missing instruction.

The Tata 1mg authenticity reference describes pharmacist involvement in dispensing and separate quality practices for medicines and diagnostics. It is a reference to that company’s stated processes, not certification of this proposed build. Agree your own approval responsibilities, required evidence and release controls with qualified professionals. Generic marketplace support staff must not alter a pharmacist’s decision merely to clear an order queue.

Catalog restrictions must survive search, substitutions and repeat orders

A prohibited item should not become purchasable through a saved basket, a search synonym or an old promotion. Model catalog eligibility by jurisdiction, provider and service type, with a recorded review process for changes. Keep medicine identity, formulation, strength and pack details explicit where relevant to the reviewed catalog. Do not infer clinical equivalence from similar names or a lower price, and do not publish patient-specific treatment suggestions as product recommendations.

If stock is unavailable, the system needs the provider’s reviewed substitution or clarification path and any required patient approval. Preserve the originally requested item and the accepted change instead of rewriting the order. Refills require a new eligibility check under agreed rules, not automatic reuse of a historical approval. Test restricted items through mobile checkout, reorder links and administrative tools, including the attempt to replace an unavailable item with an unreviewed alternative.

Provider eligibility belongs in routing, not only onboarding

A provider can pass initial onboarding and later lose eligibility for a service or location. Store reviewed credentials, their scope, expiry and the person responsible for checking them. A decorative verified badge does not explain authority. Gate new assignments on the current record and identify accepted requests requiring reassignment or professional review when status changes. Keep the evidence restricted rather than exposing credential documents to every marketplace participant.

Separate permissions for pharmacy review, laboratory administration, report release and consultation. A staff member working across branches should not gain automatic access to all patient records. Provider offboarding needs account closure, unresolved-request ownership and treatment of retained records according to applicable obligations. Ask the demonstration to expire a credential while accepted work exists. The operator should see affected requests and an accountable resolution, not silent cancellation or unrestricted continued routing.

A diagnostic slot is not a collected or accepted sample

Home collection requires service-area coverage, provider capacity, patient matching and provider-issued preparation information. The software should present instructions supplied or approved by the laboratory rather than generate medical preparation advice. Keep requested, confirmed, collector assigned, collected and laboratory accepted distinct. A calendar confirmation alone cannot prove collection. Record rescheduling, failed access and a patient identity mismatch with a clear next action for both the customer and provider.

Link the sample identifier to the intended booking and preserve handoff events under the laboratory’s agreed procedure. An unsuitable or rejected sample needs a provider-owned recollection decision and an explanation of any billing adjustment. Do not disguise recollection as a completed test or publish a report merely because the scheduled time passed. Rehearse a collector outage and a duplicate sample update so one booking cannot acquire two unrelated results.

Release reports to the right person and preserve corrections

Laboratory processing, professional review and report release are distinct milestones. Obtain the provider’s rules for release authority and patient notification. A revised report should retain its version, issuing provider and correction history instead of silently replacing a file. Use private, authenticated access and prevent public indexing of report links. Email or notification previews should not expose sensitive results to someone who only has access to the shared device.

Define who handles urgent-result communication with the laboratory and appropriate professionals; an ordinary support queue must not be presented as emergency care. The marketplace can track whether the agreed notification process occurred without interpreting a result itself. Staff should see only what their coordination task requires. Test an unauthorized report download, a corrected report notification and a laboratory outage with a visibly pending state rather than an invented completion estimate.

Consultation routing must not impersonate clinical care

A consultation requires an eligible professional, suitable service type, confirmed availability and the reviewed consent process. Confirm whether the product schedules appointments, supplies communication tools or also retains clinical records under provider responsibility. Make failed connections, clinician cancellation and incomplete sessions visible. A paid session that never connects is not automatically completed, and support should not write a clinical note on the professional’s behalf.

Explain the limits of the service before the user relies on it. Emergency requests need the operator’s reviewed direction to appropriate local assistance rather than an implied immediate response from the app. Do not add symptom diagnosis or automated prescribing as ordinary marketplace automation. These require separate clinical and regulatory evaluation. During acceptance, inspect what happens when a clinician becomes unavailable after payment and when the patient declines the proposed replacement.

Health consent is not a blanket marketing permission

A prescription submitted for dispensing does not authorize unrelated advertising, general analytics exports or disclosure to every provider. Map the purpose, recipient and necessary data for each service. Keep permissions for caregiver access, provider exchange and promotional communication distinguishable. Review retention and correction obligations with appropriate specialists, including records that cannot be deleted immediately because a lawful retention requirement applies. Avoid claims that a consent checkbox establishes universal compliance.

Log sensitive access and restrict bulk exports. Payment and delivery staff often need order identifiers, amounts or addresses rather than medical documents. Do not send health files to third-party tools by default or include them in routine error logs. Use synthetic records in testing. Demonstrate revoked access, an unauthorized export and a provider receiving only the service-specific information it needs, including after a request has been reassigned.

Reconcile pharmacy, diagnostics and consultation money separately

The patient may pay once while providers complete their work on different schedules. Retain service-level invoice, charge, refund and settlement records. Agree the basis for partial pharmacy fulfillment, cancelled collection, recollection and consultation failure before configuring fees. Keep requested, acknowledged, failed and uncertain payment states separate. Replayed callbacks must not produce duplicate refunds or settle a provider whose service remains unresolved.

The Tata 1mg health partner agreement uses different completed-order definitions for pharmacy, diagnostic and consultation services. That distinction is useful for designing your own reconciliation model; its commercial terms do not become your contract. Document your completion criteria and dispute responsibilities independently. A support credit resolves a financial issue, not a missing report, dispensing concern or professional complaint.

Accept the release using synthetic patient journeys and failed handoffs

Illustrative screens can explain the proposed interface but cannot establish licensed supply, working laboratory access, medical certification or a live clinical service. Request a guided walkthrough with synthetic patient profiles, test documents and sandbox payments. Inspect the buyer account, pharmacy review queue, laboratory booking surface and operator console. Confirm which integrations actually run, which are mocked and which require provider agreements before any launch commitment.

Buyer acceptance should cover an unreadable prescription, restricted item, expired provider credential, revoked caregiver access, rejected sample, corrected report and failed consultation connection. Add partial fulfillment and a duplicate refund callback. Verify mobile readability, keyboard access and recoverable interrupted uploads without logging health content. Record named owners for every unresolved service. Handover should distinguish agreed source deliverables, third-party licenses, operational access and professional responsibilities; software delivery does not confer permission to practice or dispense.

Bring your provider arrangements and service boundary to a health marketplace scope review. Use redacted operational examples to decide what can launch and what must wait for qualified review.

Use the delivery process to agree permission design, provider integration rehearsal and service-specific acceptance checkpoints. The goal is an explainable request-to-resolution journey, not another health storefront with uncertain responsibility behind checkout.