How JD Health’s Aries Platform Scales Internet Hospital Development

Policy Background and Market Momentum

In April 2018 the State Council issued guidelines to promote “Internet+ healthcare,” followed by a series of regulatory documents in September that formalized internet‑based diagnosis and remote medical services. By August 2019, internet medical services were included in national health insurance reimbursement, and during the 2020 COVID‑19 pandemic additional policies encouraged “no‑contact” medication purchases and electronic insurance vouchers. These regulations created a surge in demand for internet hospital platforms.

Centralized vs. Decentralized Internet Hospital Models

Two primary deployment patterns have emerged:

Centralized platform model – exemplified by JD Health’s own internet hospital, which aggregates physicians from multiple offline institutions onto a single unified platform, focusing on light‑weight consultations, chronic‑disease management, and family‑doctor services.

Decentralized (hospital‑led) model – each tertiary hospital builds its own internet hospital, enabling “online‑offline” integration such as in‑person first visits followed by online follow‑ups, and supporting functions like appointment registration, remote consultations, and prescription delivery.

Although conceptually distinct, JD Health’s technology stack bridges both models, providing core capabilities (consultation, prescription, pharmacy, settlement) centrally while exposing modular services for hospitals to assemble their own solutions.

Aries Platform Principles

The Aries platform adopts a component‑based, standardized product architecture. It treats the entire internet‑hospital business as a hierarchy of reusable assets:

Process assets – complete business flows (e.g., online follow‑up) composed of multiple pages.

Page assets – user‑facing screens (e.g., doctor list) built from “floor” components.

Floor assets – atomic UI sections that provide specific functions such as search or filter.

Capability assets – core business functions (e.g., department‑based doctor filtering, disease selection) that can be extended.

When a new hospital tenant is onboarded, the platform selects appropriate assets from this library to compose a tailored internet‑hospital system, dramatically reducing development time and maintenance overhead.

Implementation Workflow

The configuration proceeds through four steps:

Select required process components for the tenant (e.g., online consultation, health record creation, prescription delivery).

Choose page components within each process (e.g., patient record page, doctor detail page, pre‑consultation IM page).

Define the floor composition for each page (e.g., search floor, filter floor, list floor).

Configure the capability rules for each floor (e.g., filtering criteria, sorting logic, priority of appointment slots).

This top‑down to bottom‑up approach ensures that hospitals can quickly assemble a full‑stack solution that matches their specific clinical and operational requirements.

Case Studies

To date, the Aries platform has delivered internet‑hospital systems for three hospitals:

Guangzhou Medical University Affiliated Brain Hospital – Implemented online health consultation, reusing existing process and page components, achieving a one‑third reduction in development effort.

Tianjin Nankai Hospital – Built an end‑to‑end service covering appointment, online consultation, follow‑up, prescription, payment, and home‑delivery, while integrating the hospital’s HIS for seamless patient identity verification.

Tianjin Anding Hospital – Deployed a mental‑health focused internet hospital covering appointment, consultation, prescription, and medication delivery, demonstrating the platform’s ability to support specialty clinics.

Each deployment contributed new reusable components, continuously enhancing the platform’s capability set.

Future Directions

The platform will keep consolidating JD Health’s core assets, improving efficiency and value creation. Planned extensions include:

Product convergence – Transforming consumer‑facing (2C) health products such as family‑doctor services into hospital‑oriented (2H) solutions.

Scenario integration – Linking 2C and 2H business resources (patients, consultations, drugs, doctors) on a unified platform.

Ecosystem expansion – Opening the platform to ISVs to co‑create diversified solutions for a broader client base.

Contact: [email protected]