Contracted PDAs

Contracted PDAs have contractual restrictions on the data within a PDA and the data within is given joint rights - both PDA owner and an organisation. The PDA owner cannot cancel the data debit or contract without the organisation's permission. Other constraints (eg, 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 owner 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 organisation, aka not the owner 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 into a PDA.
  1. 1.
    The organisation would have a contractual agreement with the PDA owner to read/write data to the PDA. The contractual agreement is exposed via our HMIC screens, by which the contract is established by the PDA owner agreeing to it. Hence the term contracted PDA
  2. 2.
    The data stored by the organisation is related to the PDA owner and is actively maintained by the Organisation
  3. 3.
    The PDA owner may not be able to delete/modify some of the data and may also not be able to delete his entire PDA account, because of this contractual relationship with the organisation, except except when the organisation has given permission to do so, or when the business relationship no longer exists.
  4. 4.
    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 PDA may have more than one 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 organisations. It's physically the same PDA.