Healthcare Professional Compliance

Name Name of a concept, e.g. a data model concept. In contrast to terms, the name does not depend on a given context, e.g. a country-specific language.	Healthcare Professional Compliance
Short description Informal and short human-readable definition of a concept.	Lookup information about doctors, pharmacists and other healthcare professionals in connected data sources
Description Informal and comprehensive human-readable definition of a concept.	In many countries healthcare professionals or doctors require a registration in a special register, respectively need to obtain a so called medical licence. Usually with a medical licence additional restrictions or allowances come along such as permits for narcotics. CDQ connects to data sources for retrieving this kind of information. In the United States each healthcare professional (e.g. doctors) requires a valid medical license for being allowed to operate HCP. Licenses are only valid over a certain period and thus require continuous monitoring, doctors may be put on "blacklists" by the authorities as well. Additionally, data about hospitals is difficult to manage due to the vast amount of specialized departments and persons (“Prof. Dr.”) involved whose names are important to be known. Manufacturing locations of suppliers providing certain materials or substances for pharmaceutical products are to be certified and uniquely identified.

Data source overview

Data source	Full name (en) English name of a concept.	Country scope Defines a address/country a given concept is used in (or valid in, or relevant for etc.), i.e. the country-specific scope of a concept.	Short description Informal and short human-readable definition of a concept.	Category Specifies the category of a data source. The following categories are defined:<br/><code>BUSINESS_PARTNER</code>: The data source provides master data about companies.<br/><code>ADDRESS</code>: The data source provides address reference data.<br/><code>SANCTION_AND_WATCHLIST</code>: A data source that provides sanctioned or watched companies or persons.<br/><code>BANK_ACCOUNT</code>: The data source provides bank and bank account reference data.<br/><code>CERTIFICATE</code>: The data source provides information about business partner certifications.<br/><code>BENEFICIAL_OWNER</code>: The data source provides information about beneficial owners of companies.<br/><code>INSOLVENCY</code>: The data source provides information about insolvencies.<br/><code>HEALTHCARE_PROFESSIONAL</code>: The data source provides information about HCPs.<br/><code>HEALTHCARE_ORGANIZATION</code>: The data source provides information about HCOs.<br/>	Classification Framework to classify external data sources according to legal limitations and/or obligations due to integration and use of these data sources in CDQ's Cloud Services.	Release status The release status in terms of development progress or maturity of a product feature or a business capability.<br/><code>EMPTY</code> (0): No feature considered yet, just rough idea for capability.<br/><code>IDEA</code> (1): Just an idea, not yet designed in detail.<br/><code>DESIGN</code> (2): Software design ready, development not yet started.<br/><code>DEVELOPMENT</code> (3): Software development in progress.<br/><code>ALPHA</code> (4): First functional release, in terms of a Minimal Viable Product (MVP).<br/><code>BETA</code> (5): Tested by selected users.<br/><code>RC</code> (6): Release candidate, fully tested, not yet used in production by many customers.<br/><code>LIVE</code> (7): Used in production by customers, fully monitored and supported.<br/><code>DEPRECATED</code> (-1): End of life planned, but still available.<br/><code>EOL</code> (-2): End of life, historic service, no longer available.<br/><code>BROKEN</code> (-3): Service was used in production but is currently not available. However, CDQ tries to repair or reactivate it.<br/><code>DISCONTINUED</code> (-4): The data source has ceased providing updates; nonetheless, we continue to offer the most recent available data.	Integration type Documents how a data source is integrated into the CDL with respect to data gathering:* <code>REMOTE ACCESS</code>: Data is not stored on CDL side but queried ad-hoc from the data source (e.g. webservices)* <code>COPY</code>: Data is replicated on CDL side (usually already transformed into the target CDL data model)* <code>UNDEFINED</code>: not yet known	Number of records Counts the number of company records available in the data source
Data source CH.MEDREG	MedReg register of medical professions	CH		HEALTHCARE_PROFESSIONAL;BUSINESS_PARTNER		LIVE