Requirements

All of it, on open identifiers: ORCID researcher IDs, OpenAlex author IDs and US NPI provider numbers, plus each customer's own CRM IDs held in a per-customer mapping table (OQ-20). Identity resolution is built on those, and EFEVRE licenses no doctor reference database, so there is no third-party identifier to reconcile and no licence term to honour on a field.

Still held. Nothing. A paid identifier source later needs its own decision, a written licence and a source label on every field that uses it (NP-05).

Released by OQ-20, NP-05.

All of it, on the mechanism the answer chose: the customer uploads a file of engaged- expert IDs and meeting dates whenever they choose, and those experts are marked as already engaged in their lists (OQ-23). Matching uses the open identifiers and the per-customer CRM mapping table of OQ-20. A live CRM import is ruled out rather than postponed, so no read connection to a customer system is built for this.

Still held. Nothing. The engagement status stays something the customer's own users set or upload, which keeps the record theirs: this product never infers that a meeting happened.

Released by OQ-20, OQ-23, OQ-26.

All of it, and at launch it has nothing to do, which is the point: the answers license no outside data. Identity resolution runs on ORCID, OpenAlex and NPI, which are free to use, plus each customer's own CRM IDs (OQ-20), and no doctor reference database is licensed; FD-01 decides the same for enrolment data. What this requirement builds is the source register: every field carries a source label, shown on the profile and in exports, and a paid source added later needs its own decision and a written licence before a single field may use it (NP-05).

Still held. Nothing.

Released by OQ-20, NP-05, FD-01.