Operational Permission (CDQ)
DataModel:CDQ/Business Partner/Partner Profile/Hcp Profile/Operational Permission
Metadata properties
| Property | Value |
|---|---|
| The human-friendly name shown for this concept in the user interface, used instead of the technical name to improve readability and understanding. Display name | Operational Permission |
| The unique name used to identify this technical concept within the data model. Technical name | OperationalPermission
|
| Informal and comprehensive human-readable definition of a concept. Description | The operational permission of the Healthcare Professional. |
| Source of related data records or broader information, may be external reference data sources or "CDQ" as internal source. Data source | CDQ (Data source) |
| The JSON path of a data model concept along its parent concepts up to Business Partner (CDQ). JSON path | businessPartner.profile.hcpProfile.operationalPermissions[0]
|
| The broader or parent concept to which this concept belongs, used to define hierarchical or structural relationships between concepts. Parent concept | Hcp Profile (CDQ) |
| Cardinality of a data model concept, i.e., whether the concept is a single element of its parent or a list.<br/>- <code>EXACTLY_ONE</code>: Exactly one element<br/>- <code>SINGLE</code>: Optional element, just one<br/>- <code>ZERO_OR_ONE</code>: Optional element, just one<br/>- <code>LIST</code>: List of elements Cardinality | LIST
|
| Specifies the role of the concept within the hierarchy or tree-like network:<br/>- <code>ROOT</code>: the top-level concept without a parent<br/>- <code>NODE</code>: an intermediate concept with both parent and child<br/>- <code>LEAF</code>: a terminal concept without children<br/>- <code>TYPE</code>: a concrete type of a concept, e.g. <code>LEGAL_ENTITY</code> of a business partner type. Concept type | NODE
|
| Child concept | Activity Status (CDQ), Permission Status (CDQ), Practice Location (CDQ) |