Home Data Technology
Crowd Platform
Data Transaction
Medical Devices
Technology About Us Contact & Partnership
中文 EN 日本語

AI-powered matching & human follow-up

Matching works reliably only when it is done in two stages: AI filters the possible counterparties out of a pile of registrations and explains why they match; people talk through "why it does not match well enough yet" and put the authorisation scope, purpose of use and delivery method down on paper.

Multidimensional fit score Candidate list & reasons Human follow-up by consultants Delivery method options
Matching · Matching mechanism

Registered on both sides, aligned by the matching engine

Matching is not "recommend because the keywords are the same". It looks at business dimensions and compliance dimensions at the same time — a pairing that matches perfectly on business but cannot be implemented on compliance wastes time for both sides.

Supplier registrationResource type · Domain topic · Coverage · Update frequency
Authorisation and masking statusSource and authorisation chain · masking · tradeability assessment
Delivery capabilitySupported delivery methods and technical requirements
AI matching engine Matching
Demand-side registrationUse scenario · Required fields · Scale and timing expectations
Compliance requirementsWhether ethics or regulatory materials are needed · whether data must stay within its domain
Delivery requirementsUsable but not visible · Interface calls · Private deployment · Reports
Output 01

Candidate match list

A list of candidate counterparties ranked by fit score, each with matching reasons and a gap explanation, making it easy to judge quickly which are worth pursuing.

Output 02

Gaps and suggestions for filling them

Point out exactly where the gap is: insufficient field granularity, an inadequate time span, a mismatched authorisation scope, or a missing type of compliance material.

Output 03

Possible paths forward

For feasible pairings, it gives possible delivery methods and points to note, for consultants to confirm further during human follow-up.

Dimensions · Matching dimensions

Six dimensions, determine the fit score

Every dimension has three verdicts — "match / partial match / no match" — and a partial match comes with suggestions for alternatives.

Domain & topic
Whether they point to the same disease-specific direction or research topic, for example infertility treatment, pelvic floor rehabilitation or follow-up management
Data form
Structured records, imaging, waveforms, follow-up questionnaires, text and medical records, as well as governance and annotation services
Coverage
How well the time span, sample size and number of institutions match, including an alternative assessment of "slightly smaller but usable"
Fields & granularity
Whether the required fields listed by the demand side are covered and whether the granularity (single record / treatment course / aggregate level) is sufficient
Compliance status
Whether the authorisation chain is clear, whether masking is complete, whether the use scenario is well defined and whether data types requiring separate assessment are involved
Delivery & timeliness
Whether the delivery method can be integrated and whether the expected timing matches a realistic pace
Matching results are used only for screening and advice, and do not constitute a transaction condition, a price commitment or a compliance conclusion. Whether to proceed and on what terms is agreed by both parties during human follow-up, with the necessary procedures completed as compliance requires.
Limits · What AI can and cannot do

Put AI where AI belongs

Two things are most feared in matching: one is "recommended but unable to explain why", the other is "negotiations fail without knowing why". The former goes to AI, the latter to people.

What AI does

Automated
  • ✓Standardise structured registration information into comparable dimension descriptions
  • ✓Calculate multidimensional fit scores and output a ranking to narrow the field quickly
  • ✓Generate matching reasons and a gap explanation so the conclusions are explainable
  • ✓Identify clearly unworkable combinations and avoid wasted communication
  • ✓Recalculate and update matching results when new registrations come in

What people do

Human Follow-up
  • ✓Clarify the real needs and constraints that cannot be written on the registration form
  • ✓Judge whether a "partial match" is worth pursuing and what needs to be added
  • ✓Help define the authorisation scope, purpose of use and term of use
  • ✓Coordinate the technical, legal and business sides of both parties to form an executable proposal
  • ✓Advance compliance assessment, delivery arrangements and process records
Workflow · From matching to delivery

Five steps, Every step produces an output

The workflow is designed so that "you always know what the next step is": the input, output and owner of every stage are clear.

Standardisation of registration information

Turn the free text registered by both sides into structured dimension descriptions and fill in missing key items (such as use scenario and field list). Output: a standardised registration file.

Compliance screening

Check how well defined the scenario is and how clear its boundaries are to judge whether the preconditions for progress exist; data types requiring separate assessment are flagged in advance. Output: a screening conclusion.

AI fit score calculation

Calculate and rank across six dimensions, generating a candidate list with matching reasons and flagging the specific gaps of a "partial match". Output: a match list.

Consultants follow up separately

We speak with each side separately to verify that the need is genuine, that the resource is genuinely available and that the compliance conditions hold, adjusting the plan or widening the candidate pool where necessary. Deliverable: a follow-up plan.

Compliant delivery & record-keeping

Choose the delivery method according to the data tier and complete delivery in a secure, trusted environment, producing a record of the transaction and delivery process. Output: delivery records and supporting documents.

Delivery · Delivery method

Delivery does not mean "copying the data away"

Choose the delivery method according to data sensitivity and use scenario. Most medical data scenarios prefer "usable but not visible" — the demand side gets the results while the data holder retains control.

Sandbox

Data usable but not visible

The demand side completes analysis or modelling in a controlled sandbox environment: it can use the data and obtain results, but cannot export or take away the raw data. Suitable for scenarios of higher sensitivity with a clearly defined purpose of use.

  • Scope of use and operation types are constrained by policy; operations beyond authority are blocked
  • Results are taken out only after review, preventing raw records from leaking out
  • The whole process is recorded, traceable to the specific operation and time

This is the most common delivery form in medical data scenarios: the demand side gains the analytical value while the data holder retains control over the data.

Interface

Interface calls within the agreed scope

Providing specific query, verification or computation capability as an interface, with metered call volumes, verifiable purposes of use and permissions automatically revoked when the agreement expires.

  • Only the agreed fields and agreed frequency are opened up; no full-dataset queries
  • Call logs are auditable; abnormal calls can trigger alerts and be blocked
  • Suitable where the capability needs to be embedded in your own system and called continuously

The interface approach turns "data delivery" into "capability calls" — an effective way to reduce the risk of data flowing out.

Model & Agent

Model & agent capability delivery

Delivering capability as a disease-specific model or a packaged agent, supporting controlled service calls or private deployment and meeting the requirements of a domestic IT environment and of data not leaving its domain.

  • Private deployment: the capability is deployed into the demand side environment and data does not flow out
  • Controlled calls: used within the authorisation scope, with metered call volumes
  • Delivered together with model documentation, scope of application and usage boundaries

Model-based delivery must also state the scope of the training data and the boundaries of application, so as to avoid out-of-scope use.

Dataset

Masked dataset delivery

Delivered as a dataset after the compliance assessment, authorisation confirmation and masking have been completed. Suitable where sensitivity is manageable, the scope of use is clear and a complete compliance chain is already in place.

  • Compliance assessment and authorisation scope confirmation are completed before delivery
  • The data documentation sets out the definitions, scope, gaps and limitations
  • The term and scope of use are written into the agreement and handled as specified on expiry

Dataset delivery has the highest threshold, so it is better suited to being part of a long-term collaboration rather than a one-off action.

* The delivery method must match the sensitivity of the data, the authorisation scope and regulatory requirements. Where human genetic resources or highly sensitive personal information are involved, the corresponding procedures must be completed as required before proceeding; the specific method is subject to the agreement between the parties and the relevant regulatory requirements.

FAQ

About the matching mechanism

After a match is found, will the two parties contact each other directly?

Consultants first speak with each side separately to confirm that the demand is genuine and the conditions feasible, then arrange contact according to the wishes of both parties. This avoids wasted effort when "direct contact reveals that it is simply not suitable", and makes it easier to clarify the authorisation scope and compliance conditions at an early stage.

What if none of the matching results are suitable?

Consultants will report where the gaps lie and offer optional adjustment paths: widening or narrowing the candidate pool, adjusting field granularity requirements, switching the delivery method, or first completing a certain type of compliance material. If they judge that the market genuinely lacks a match, they will say so honestly rather than force a recommendation.

Who sets the price? Does the platform get involved in pricing?

Prices are agreed between the two parties to the transaction; the platform does not set prices unilaterally. Consultants can help both sides clarify the pricing logic and the key variables that affect price (data scope, update frequency, scope and term of use, exclusivity and so on), giving the negotiation a common basis.

What does the transaction record-keeping include?

This covers registration and initial-screening records, the matching conclusion, the key confirmations made during matching and follow-up, records of the delivery method and data destination, and any supporting documents required. The purpose of keeping a trail is to be able to answer where the data came from, where it went, and the scope within which it was used.

Can I specify "no counterparties of a certain kind"?

Yes. At registration you can list in the notes any competitive relationships or existing cooperation constraints to be avoided; matching and follow-up will exclude the corresponding counterparties accordingly, and the information is used only for internal judgement within this process.

Register first, so matching can be targeted

Register your resources or needs; AI narrows the field first, then a professional consultant makes the plan clear. We will confirm the next step with you after the initial screening.