> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/integrations/identity-verification/epic-identity-verification-in-mychart-and-epiccare-link/configuring-1kosmos-as-an-identity-verification-vendor-in-epic.md). # Configuring 1Kosmos as an identity verification vendor in Epic After creating your OIDC client and workflow, you will need to request a download of the 1Kosmos application in Epic. This can be done in parallel with the rest of set up. Reach out to your 1Kosmos representative for assistance. After 1Kosmos approves the application download, you will use the information provided within Epic complete the integration set up. \ \ For Epic’s documentation on adding identity verification for MyChart, see [Toolbox ID Verification for MyChart.](https://galaxy.epic.com/?#Browse/page=1!68!50!100366832) For Epic’s documentation on adding identity verification for EpicCare Link, reach out to your Epic representative. #### Client ID and client secret These are generated when you create the OIDC client. You can find them in the application details page. #### Well-known configuration URI Navigate to Settings > General > Authorization Server Your Well-Known Config URI will be formatted as:\ [https://\.1kosmos.net/oauth2/community/default/.well-known/openid-configuration](about:blank) Replace \ with your actual tenant name. #### Scopes * openid * profile * identity\_assurance * idv\_flow\_\[access\_code]. Replace access\_code with the access code generated during workflow creation. #### Branding information * Button Color: #5342FF * Text Color: #FFFAF1 * Button Logo: [1Kosmos Logo](https://6858402.fs1.hubspotusercontent-na1.net/hubfs/6858402/Brand%20Assets/1K-Wordmark-White.webp) #### Expected user claims After an identity verification, 1Kosmos returns the claims from the workflow back to MyChart. You configure how these claims are returned in the JSON snippet in your OIDC Client. For example, if you use the suggested JSON in [Setting up an OIDC Client in 1Kosmos](broken://spaces/5DFSjLrGww16mwRQ5csY/pages/3j5VCzDEovit1L0eCToo), the return might look like this: ``` { "sub": "USERNAME", "firstname": "FIRST_NAME", "lastname": "LAST_NAME", "birthdate": "BIRTHDATE", "ssn": "SSN", "at_hash": "AT_HASH_VALUE", "aud": "AUDIENCE_VALUE", "exp": EXPIRATION_TIMESTAMP, "iat": ISSUED_AT_TIMESTAMP, "iss": "ISSUER_URI" } ```
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.1kosmos.com/integrations/identity-verification/epic-identity-verification-in-mychart-and-epiccare-link/configuring-1kosmos-as-an-identity-verification-vendor-in-epic.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.