View the Final Standard
The standard defines the following:
- HCP Registration – The required user-entered data and process flow for new HCP registration.
- HCP Verification – The process whereby an HCP is verified as either a medically licensed or non-licensed medical professional.
- Identity and Authentication – The process flow and token exchange protocols for authentication and availability to third parties.
- Identifiers – The minimum set of identifiers and their qualities that must be associated to each HCP.
- Authoritative HCP Data – The qualities an HCP data set must exhibit when used as a part of HCP verification.
- Global Support – The availability and operational requirements for end-user support of HCPs during registration and verification.
- Audit Requirements – The required audit and reporting capabilities.
- Data Security and Trust – The security programs and standards that must be adhered to.
- Country-to-identifier Mapping – The standard identifiers by country used as a part of the HCP verification process.
Consent and Communication Preferences
Align Biopharma will establish a standard for consent and communication preference management so that there is consistency in how HCPs specify communication preferences with each company.
The standard will define the following:
- Consent – A common definition of what and how an HCP can opt-in and opt-out of communications from each company.
- Dimensions of Preferences – A common definition of communication preferences across dimensions such as geography, product, information type, and communication channel. This definition will also establish a framework that allows these dimensions to evolve to future needs of both HCPs and the companies serving them.
- User Experience – A standard user experience for HCPs when specifying their consent and communication preferences by company. The goal is to provide the HCP an intuitive, consistent experience across all service providers and life sciences companies.
- Data Model – A standard data model for storing HCP consent and communication preferences. With a unified data model, the integration of this data across enterprise systems will be easier, more cost-effective, and less error prone.
- Interpretation – A standard way for companies to leverage HCP consent and communication preferences. Once these data are captured, the semantics of what the preferences and consent mean must be interpreted consistently by any service/company wishing to act upon the information. Integrated systems leveraging this data must have a common understanding of what the data means.