09 · Data · Notion
User Data Consent
Request and capture users' consent for personal-data use inside the Unimed ecosystem, sending the response to AWS and supporting a relational-to-non-relational database decision.
Project context — organizations, products, and platforms evidenced in the source
UnimedPPrivally
- Role
- Back-End · Solutions Architect · Dev Ops
- Domain
- Data
- Sources
- Notion
- Published artifacts
- 5
Evidence archivePrivally wordmark cover.
Context
The problem and its boundary.
Request and capture users' consent for personal-data use inside the Unimed ecosystem, sending the response to AWS and supporting a relational-to-non-relational database decision.
Decisions & deliverables
- Repository metadata for privally-management-consents (currently private)
- Database comparison
- Database structure and modeling document
- DynamoDB single-table key design
- Entity model covering Organization, Asset, Identifier, Person, Consent and Session
Technology
- DynamoDB
- AWS Lambda
- Docker
- Node.js
Evidence archive
Real diagrams, interfaces and documents.
Open any artifact to inspect the full local image.
Public references
Private repository · metadata authorizedalexcfreitas/privally-management-consentsWhat this archive can prove
Published authorship. Claims proportional to the source.
- No detailed responsibility-by-activity narrative, quantified result, traffic/consent volume, compliance claim or deployment date is present.
- The complete document is rendered as page content but was not recovered as a standalone file.
- The Notion extraction did not analyze the linked GitHub repository.