update

Fastenโ€™s ๐๐ซ๐ข๐ง๐  ๐˜๐จ๐ฎ๐ซ ๐Ž๐ฐ๐ง ๐ˆ๐๐ž๐ง๐ญ๐ข๐ญ๐ฒ capability is now live

Fastenโ€™s ๐๐ซ๐ข๐ง๐  ๐˜๐จ๐ฎ๐ซ ๐Ž๐ฐ๐ง ๐ˆ๐๐ž๐ง๐ญ๐ข๐ญ๐ฒ capability is now live

Donโ€™t make patients prove themselves twice.ย 

Fastenโ€™s ๐๐ซ๐ข๐ง๐  ๐˜๐จ๐ฎ๐ซ ๐Ž๐ฐ๐ง ๐ˆ๐๐ž๐ง๐ญ๐ข๐ญ๐ฒ capability is now live!ย 

Fasten lets patients share records without completing identity proofing a second time when your organization uses a supported Credential Service Provider like CLEAR, ID.me, or Persona.

That means your team can keep the identity stack you already use.

Patients verify identity in your product first, and when theyโ€™re ready to share records, Fasten uses that verified identity to continue the record retrieval flow.

๐˜•๐˜ฐ ๐˜ด๐˜ฆ๐˜ค๐˜ฐ๐˜ฏ๐˜ฅ ๐˜ด๐˜ฆ๐˜ญ๐˜ง๐˜ช๐˜ฆย 
๐˜•๐˜ฐ ๐˜ด๐˜ฆ๐˜ค๐˜ฐ๐˜ฏ๐˜ฅ ๐˜ฅ๐˜ฐ๐˜ค๐˜ถ๐˜ฎ๐˜ฆ๐˜ฏ๐˜ต ๐˜ค๐˜ข๐˜ฑ๐˜ต๐˜ถ๐˜ณ๐˜ฆ
๐˜•๐˜ฐ โ€œ๐˜ฅ๐˜ช๐˜ฅ๐˜ฏโ€™๐˜ต ๐˜ ๐˜ข๐˜ญ๐˜ณ๐˜ฆ๐˜ข๐˜ฅ๐˜บ ๐˜ฅ๐˜ฐ ๐˜ต๐˜ฉ๐˜ช๐˜ด?โ€ย 

Teams shouldnโ€™t have to replace their identity stack just to enable medical record access. ๐๐ซ๐ข๐ง๐  ๐˜๐จ๐ฎ๐ซ ๐Ž๐ฐ๐ง ๐ˆ๐๐ž๐ง๐ญ๐ข๐ญ๐ฒ lets record retrieval fit into the product and patient journey youโ€™ve already built.

For implementation details, the full technical guide is here: https://docs.connect.fastenhealth.com/identity-proofing/introduction