argonautproject / scheduling

Argonaut Scheduling and Appointments: This project supports basic patient and provider access to a provider's calendar and appointment requests, including APIs and guidance for searching and publishing a providers schedule andrequesting, cancelling or updating an appointment.
http://www.fhir.org/guides/argonaut/scheduling/
15 stars 2 forks source link

What is the definition of "System level trust" #51

Closed Healthedata1 closed 6 years ago

Healthedata1 commented 6 years ago

We discussed this concept in the context of provider scheduling across systems. Is this concept already covered in FHIR or Argonaut? like here: http://hl7.org/fhir/security.html#http or here: http://hl7.org/fhir/us/core/security.html

I thnk its actually is closer to Argonaut Use Case 5 ("Provider using EHR A access patient record held in EHR B Introduction In this use case, the clinician uses an EHR application (EHR A)"

Bottom line is we will need to say a little more about this before publishing the guide.

Healthedata1 commented 6 years ago

response from cooper: "System level trust really just means that you are using something like OAuth2 client credentials, or a service account."

look at SMART backend services...