Contracted PDAs
Contracted PDAs have contractual restrictions on the data within a PDA and that SSData within is given joint rights – to both PDA user and an organization. The PDA user cannot cancel the data debit or contract without the organization's permission. Other constraints (e.g., not being able to delete the PDA) would also apply.
Conventionally, a user would be online and using an app to read/write data from/to the PDA. The PDA user would be the initiator of this data i/o process. In a contracted PDA, the initiator of the data exchange would be the business or organization, aka not the user of the PDA. This is in cases where pDAs are used, for example, for HR purposes where companies would need access to store and access their employee records, or for medical records where medical staff can update records on a PDA.
The organization would have a contractual agreement with the PDA user to read/write data to the PDA. The contractual agreement is exposed via our HMIC screens, and the contract is established by the PDA user agreeing to it; hence the term
contracted PDA.The data stored by the organization is related to the PDA user and is actively maintained by the organization.
The PDA user may not be able to delete/modify some of the data and may also not be able to delete their entire PDA account, because of this contractual relationship with the organization, except when the organization has given permission to do so, or when the business relationship no longer exists.
The scope of a contract would be the contents of 1 namespace. i.e. 1 contract would allow an organisation to access the data of 1 namespace.
Technically, although a PDA may have more than 1 namespace, by convention it is usually 1 namespace for 1 application. Of these namespaces, some may be configured as contracted, allowing the above. A contracted PDA is only called such, because it has 1 or more namespaces which has contracts with organizations. It's physically the same PDA.
Last updated