My next question: Is any difference between the patient that registered by https://foomedical.com/register and invited through https://app.medplum.com/admin/invite? what we see right now, that the patients that registered through foomedical is not able to login using https://app.medplum.com/oauth?client_id=client_id_value&redirect_uri=https%3A%2F%2Fpatient-ehr.domain.com&response_type=code&scope=openid&state=2022-12-02T23%3A34%3A30Z only when I send invite then their are fine to sign in

There should be no difference between the two flows. I'll take a look

codex health

Sorry , for foo medical, are you using the url

https://foomedical.com/

, or a different url?

yes,

https://foomedical.com/

and click Sign Up button

Thanks! So a couple of clarifications - https://foomedical.com/ is a public version of the Foo Medical project that is available to anyone. - One the backend, it is connected to a Medplum Project that is shared across all users (not specific to Codex Health). So when you register a new patient, they show up in the shared project, not the

Codex Health Sandbox

project. - In contrast https://app.medplum.com/admin/invite? invites people to the current project that you are logged into (e.g. the

Codex Health Sandbox

project) To use Foo Medical against your own project, you'll have to fork it, change the

VITE_MEDPLUM_PROJECT_ID

in the environment, and deploy it to a site you own. Vercel actually makes this pretty easy to do 🙂 . You can find the instructions here: https://github.com/medplum/foomedical#deploying-your-app

ok, I understand