How it Works
A World of Mobile Health Data
Connect
User connects their device(s) and/or app(s) and grants explicit permission for the transfer and use of data
Connect: Core API & Direct Connection
Exchange of unique, anonymous IDs and access tokens allows Validic to transfer fully de-identified data between device/app vendors and patient portal. Through this process, Validic uses and meets all criteria in employing the Safe Harbor method of de-identification, described in §HIPAA 164.514(b)
Action
Users generates data, which is then passed to Validic
Impact
Validic impacts both the incoming data, and the outgoing connection via their standardized API
Impact the Data Source: Once the data is received by Validic it is timestamped (at sync, and at creation), validated, normalized, and standardized.
Impact on Connection: Validic and ACS MediHealth stay up-to-date with all business relationships with vendors, changes to APIs (endpoints, formats, etc.), and maintenance issues.
Deliver
US-based servers with full redundancy, active intrusion monitoring and vulnerability scans, data encrypted (in-transit and at rest to 256-bit AES), fully HIPAA compliant, FDA-listed Class I Medical Device Data System (MDDS), and de-identified to the "Safe Harbor" standard.
MEDITECH mHeatlh & PGHD Delivery:
All MEDITECH platforms can accept delivery based on the dotted lines below, MEDITECH 6.15 platforms can accept both dotted and solid lines below.
