MedicationRequest and DiagnosticReport

[Fred Doughty]

Hello,

I require access to both endpoints (MedicationRequest and DiagnosticReport).  However, Cerner's r4 implementation does not contain a DiagnosticReport, and dstu2 implementation does not contain MedicationRequest.

Please advise how one would be able to access both endpoints in one session.

[Aaron McGinn (Cerner)]

If you provide the app ID or client ID and which scopes (read/write) you want added, I can do that for you.

-Aaron (Cerner)

[Fred Doughty]

Thanks Aaron,

I have two clientIds I need this functionality on:

ClientId1: 506b1f0e-9ce4-43f7-b7f1-ea7bfabf4e2a
ClientId2: a82fb090-a701-4152-b7f1-4074558b0a24

Could you please add DiagnosticReport to our r4 implementation, and MedicationRequest to our dstu2 implementation?

Also, for when we will need to do this in our production environment, is this Google group a sufficient channel for posting such requests in the future?

Thanks!! 

[Fred Doughty]

Only need read for the scopes.

[Aaron McGinn (Cerner)]

Both of these IDs were DSTU2 and already had DiagnosticReport.read.

When you go through validation, we will work with you on uCern to ensure we have the correct scopes in production.

-Aaron (Cerner)

[Fred Doughty]

Yes, please take the time to understand what I am asking.

When it is set to DSTU2, I do not have access to MedicationRequest, which I need.

When it is set to r4, I do not have access to DiagnosticReport, which I need.

I would like both endpoints to be available for both specs.   If it is not possible to add it on both specs, then could you please add DiagnosticReport to r4 for us?

Thank you

FD

[Aaron McGinn (Cerner)]

The apps were set as DSTU2 and had DiagnosticReport.read already. I added MedicationRequest.read to both of them, and you should be able to use it now. We do not yet have DiagnosticReport on R4, and MedicationRequest replaces MedicationOrder and MedicationStatement from DSTU2.

-Aaron (Cerner)

[Fred Doughty]

Thanks, Aaron.  I'm still not seeing it.  Is there a delay in propagation time?

[Fred Doughty]

The above screenshot is set for dstu2.  MedicationReport still not available.

[Aaron McGinn (Cerner)]

The MedicationRequest scope will not show in the console, but will allow access during the authorization workflow when you provide that scope.

-Aaron (Cerner)

[Fred Doughty]

Hi Aaron,

Thanks for your continued support on this.  The change you made has gotten me a little further.  Before, I was getting an error saying "insufficient scopes".  That appears to be resolved, but I am now receiving a 404 from MedicationRequest endpoint:

[Aaron McGinn (Cerner)]

You will have to change the "dstu2" in the URL to "r4" as MedicationRequest is an R4 resource.

-Aaron (Cerner)