Methylation Integrations
Methylation testing integrations should be evaluated by the workflow they actually support. Before relying on an integration, confirm the current export format, data fields, privacy terms, access controls, and whether the receiving system can use the report or data as intended.
What to verify before connecting a workflow
Supported formats
Confirm which report or data export formats are currently available and whether the destination system accepts them.
Data boundaries
Identify which fields are transferred, who can access them, and whether genetic information is treated differently from ordinary account data.
Clinical responsibility
A workflow connection does not turn a consumer genetic result into a diagnosis. Clinical interpretation remains a separate professional task.
Design the workflow around the real report
Start with the actual output: PDF report, structured export, or another supported format. Map where it is stored, who reviews it, how corrections are handled, and how a user can request support. Do not assume a specific EHR, API, or vendor connection unless it is explicitly documented as supported.
Privacy deserves its own integration review
Genetic data can be sensitive. Review the privacy policy and ask how permissions, third-party processing, retention, deletion, and account access apply to any connected workflow.
Confirm current integration details before implementation
Use documented workflow information and contact Methylation.us when you need confirmation about a specific integration or export path.