Re: Dr. Chrono - Details for API integration

[Maxwell Cuculich]

Hi Rashid - I'll be forwarding this along to the correct department and point you in the right direction (API group CC'd on this message) 

- Max 

On Thu, Sep 28, 2017 at 2:13 PM, Rashid Toure <ras...@pager.com> wrote:

Hi Maxwell,

As you may be aware we are working on our 2nd Dr. Chrono instance which will be integrated with our system. our engineers are looking for below info to proceed with the API integration.

We’ll need the:
1. Oath ClientID
2. Oath Client Secret
3. Access Token
4. Refresh Token

5. Site /  Instance name

Thank you,

Rashid Toure

Integration
ras...@pager.com
929-259-4447

pager.com

Confidentiality Notice: 

This e-mail transmission, and any documents, files or previous e-mail messages attached to it, may contain confidential information. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify secu...@pager.com or by telephone at (646) 535-9481, and destroy the original transmission and its attachments without reading them or saving them to disk.

--

Maxwell Cuculich / Sr. Sales Representative 

max...@drchrono.com / (650) 922-2666

[Denis Malinovskiy]

I think there's some confusion here:  you can get all this information yourself creating a drchrono account and navigating to Account/API menu.

--
You received this message because you are subscribed to the Google Groups "drchrono Medical Healthcare API SDK" group.
To unsubscribe from this group and stop receiving emails from it, send an email to drchrono-api...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Denis Malinovskiy

Software Engineer, drchrono

[Michael Nusimow]

Hi Rashid,

  We have a lot of open source projects on Github that use the drchrono API: e.g.: https://github.com/drchrono/api-example-django

Just search for "drchrono" in public repos in Github.  Most are written in Python, could be a great starting point to look at some of those and just copy the OAuth code which usually takes some time and pain to get setup the first time.

[Michael Nusimow]

H Rashid,
Just closing the loop here, each “Practice Group” in drchrono has a different API key. So if your “second instance” is a different practice group you can get the client secret when logged into this second practice group.

On Fri, Sep 29, 2017 at 06:59 Rashid Toure <ras...@pager.com> wrote:

Hi Michael,

We are not new to Dr. Chrono APIs. we have previously deployed the APIs (Patient create and appointment booking) successfully on to our first Dr. Chrono instance. Are you suggesting that client and client secret are the same for this new Dr. Chrono instance that we recently implemented?

Thank you, 

Rashid Toure

Integration
ras...@pager.com
929-259-4447

pager.com