Dataswift's Resource Repository Design

Design Patterns using PDAs

Documents

1:1 Identity and Storage

1:1 Identity and Storage

Last updated: 3 years ago

1:2-1 Identity, Storage, Analytics, Regulated PDAs

1:2-1 Identity, Storage, Analytics, Regulated PDAs

Last updated: 4 years ago

2:1:1 Identity, Storage, Other Data

The app will have permission to read/write into the app’s own folder (namespace) with no access to the other folders in the PDA. The app will redirect to PDA for PDA owner to install the dataplug which will be acquire data from elsewhere. The dataplug will input information into the user's PDA which the app may utilize. #### Kyrdafit Case study: The Kyrdafit app is using strava data to collect an individual's cycling and running data, in order to give the individual feedback on training goals. This architecture sees the Kydrafit app store personal data of the individual within the PDA using the strava data plug.

Last updated: 4 years ago

2:2:1 Identity, Storage, Other Data and Analytics

The app stores sensitive data on the individual within a PDA and uses the data plug to enable the user to get data into their PDAs. App may feed some of the information into a product server to do further analytics or store non- sensitive user data as needed. ### OneZero-Me Case study: OneZero-Me provides risk scores for insurers and lenders based on alternative data. They have an app which is a client facing ‘financial passport’ app and a facebook dataplug. The dataplug feeds information to the PDA and the product server is able to take the information to do analysis on the individual to see the risk of lending to the individual user. This is then portrayed back via the app.

Last updated: 4 years ago

1:2 Identity, Storage and Analytics

1:2 Identity, Storage and Analytics

Last updated: 4 years ago

1:2-1:X Identity, Storage, Analytics, Contracted PDAs, Double-sided

### Use case: Organisations using PDAs for employee or student records The app populates information into contracted PDAs. Contracted PDAs have contractual restrictions on PDA owners for specific folder access and the app folder within the PDA is given joint rights - 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. The product server is able to produce analytics or simply direct/merge information. Benefits of this solution include but are not limited to; organizations having control of information pertaining to them in the organization’s folder via the contracted PDAs functionality, as well as data that is shared with the organisations product server can produce analytics to enrich enterprise systems to benefit wider organisation. App information and contracted PDA information can be combined by product server. PDA owners are still private across all other folders in the PDA

Last updated: 4 years ago

2:2-1:1 Identity, Storage, File Storage and Analytics

There are two apps in this model, one facing businesses and another facing consumers. The apps feed information into the PDA and use a file storage add on as well. The information between the apps goes to a product server which provides further analysis and is able to feed information back out into the two apps or straight to PDA. The product server is also able to send further information out to enterprise systems to enrich other systems in that organisation. #### Edari Case study EdariOne are working to share candidate CVs with relevant organisations who are looking to hire. The candidate submits the CV via an app and the organisations view the candidate details via another app. The above architecture depicts how this is done. One of the apps is for the candidates to submit CVs, which stores data of the individual in the PDA and another app is for businesses to view the CVs. Edari have a product server on their side which they use to produce analytics from the CV content and push that back out to the app that allows organisations to view a candidate's information. This product server will also enrich other enterprise systems for Edari to share insights and knowledge. There is also a file storage add-on for the PDA.

Last updated: 4 years ago

1:2-1 - Identity (Blind), Storage, Edge AI, Analytics

1:2-1 - Identity (Blind), Storage, Edge AI, Analytics

Last updated: 4 years ago

1:2-3 Identity, Storage, Analytics, 3 PDA Types

#### Presumptions on this architecture: ### Use case: The nursing home app This app gives nurses the ability to store and keep records of patients electronically rather than hard copies. These patient records need to be accessed by multiple nurses at different times in order to administer medication to the patients and to keep track of various aspects whilst the patient is in care. The above architecture shows a single app that nurses will be able to interface with to record data. All patient related data will be kept in regulated PDAs that are HIPAA certified. Contracted PDAs are given to nurses who will have access to multiple namespaces (Regulated PDAs) so they are able to read/write information into these PDAs. Guardians with default PDAs are given permission by the nursing home that owns the nursing app to view data within the regulated PDA. Regulated, Contracted and default PDAs will talk to the product server possibility giving information for analysis e.g. which patients need tending to or next round of medicine to be administered, confirmation of the guardian providing access to the patients. Regulated PDAs may have other rules for auditing purposes. The product server will produce the necessary analytics and push information back out to the app which nurses interface with. Benefits of this solution include; HIPAA certified backend, access for nurses to multiple PDAs (namespaces), with access control by the nursing home.

Last updated: 4 years ago

2:2-2:X Identity, Storage, File Storage, Other Data, Edge AI, Analytics

#### Presumptions on this architecture: There are two apps in this model, one facing businesses and another facing consumers. The apps feed information into the PDA and use a file storage and tools add on. The information between the apps goes to a product server which provides further analysis and is able to feed information back out into the two apps. The product server is also able to send further information out to enterprise systems and other systems to enrich other systems in that organisation. #### Drug Trial Matching Case study: The app connects individuals with illnesses to various medical drug trial providers to test drugs for specific illnesses that are still being developed. The architecture above depicts the two apps: one interface for individuals with specific illnesses and one for medical service providers who run drug trials. As the user app has to store sensitive data, the information is stored in the PDA with file storage and tools (SHE Functions) as add-ons. This information is then shared with a product server to produce analytics and match the individual with the relevant drug trial. The product server is also able to enrich enterprise systems for wider organisations to give them useful statistics as well as other systems that may or may not be facing the outside world

Last updated: 4 years ago