Stream: cds hooks
Topic: Jan 2018 Connectathon
Kevin Shekleton (Dec 07 2017 at 21:08):
I provided this information in my recent mailing list post but I wanted to call it out separately here since I don't wnat anyone to miss this.
The January 2018 Connectathon is coming up on January 27-28, 2018 (Saturday & Sunday). The Connectathon is two full days this time. Additionally, we will be having a breakout session Friday night (January 26) from 4-6p instead of holding it during the Connectathon.
Registration and logistics information is available here. If you plan on attending, please add yourself to our Connectathon attendee tracking sheet.
We're planning out our scenarios for the CDS Hooks track but we know the major focus will be on the 1.0 release as this is our last Connectathon prior to release. If you have other ideas or feedback, please let us know. Thanks and I hope to see you all there!
Kevin Shekleton (Jan 26 2018 at 16:24):
Hi everyone! For those who are in New Orleans for the Connectathon this weekend, I wanted to remind everyone that we are meeting this afternoon from 4-6p in the Kabacoff room. We'll be discussing the Connectathon this weekend, the security assessment that is wrapping up, and a couple of 1.0 issues.
Hilton New Orleans Riverside
2 Poydras St, New Orleans, LA 70130
Kabacoff room (in the Riverside building) - a map of the hotel is here
We will post the slides for those that can't make it. As always, any offline discussion of any Github issue will be summarized on the Github issue.
Kevin Shekleton (Jan 26 2018 at 17:19):
For those of you who are't on our mailing list or don't receive messages as they are posted, here is a link to the post I just sent regarding logistics for the Connectathon this weekend.
Kevin Shekleton (Jan 27 2018 at 14:36):
Welcome to New Orleans everyone! For those here at the Connectathon, the CDS Hooks tables are 28, 29, 37, & 38. Those 4 tables are all together at the very front of the ballroom
Kevin Shekleton (Jan 27 2018 at 14:37):
We have nifty CDS Hooks table tents on each of the tables too so you should be able to find our motley crew easily :-)
Kevin Shekleton (Jan 27 2018 at 15:13):
Thank you to everyone who was able to make it out to our CDS Hooks breakout meeting yesterday from 4-6p. We had a great turnout (~26 people!) and there was a lot of great discussion. The slides from the meeting can be found here.
Kevin Shekleton (Jan 27 2018 at 15:57):
This weekend we have 6 (!!!) CDS Hooks sandbox implementations for you to integrate your CDS Service with. Allscripts, Cerner, Epic, eClinicalWorks, and T-System all have developers here and can help you integrate into their respective EHRs. Before integrating with an EHR vendor, make sure to get your CDS Service working in our open source Sandbox at http://sandbox.cds-hooks.org
Grahame Grieve (Jan 27 2018 at 16:09):
@Kevin Shekleton : what will be new card type code for system errors?
Grahame Grieve (Jan 27 2018 at 16:12):
btw. test.fhir.org/r3/cds-services implements order-review
Kevin Shekleton (Jan 27 2018 at 17:11):
@Grahame Grieve - We're adding a new error indicator value for cards now (see https://github.com/cds-hooks/sandbox/issues/94)
Kevin Shekleton (Jan 27 2018 at 17:11):
@Grahame Grieve - I will let you know when it is deployed to the Sandbox
Grahame Grieve (Jan 27 2018 at 17:20):
ok thanks. I'll let you know when I've deployed it
Nikolai Schwertner (Jan 27 2018 at 17:20):
@Grahame Grieve I was unsuccessful in adding your http://test.fhir.org/r3/cds-services endpoint to the CDS Hooks sandbox at http://sandbox.cds-hooks.org. The error I am getting is Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://test.fhir.org/r3/cds-services. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Could you add CORS headers to your services?
Patrick Haren (Jan 27 2018 at 17:26):
btw. test.fhir.org/r3/cds-services implements order-review
are there any sandboxes implementing the order-review hook?
Grahame Grieve (Jan 27 2018 at 17:29):
sigh. the cross origin headers were being missed - I'll let you know when I upgrade it
Grahame Grieve (Jan 27 2018 at 18:36):
upgraded - should be all good. The server has CORS headers and returns an error card if there's a system error
Kevin Shekleton (Jan 27 2018 at 19:49):
@Grahame Grieve - The CDS Hooks Sandbox (sandbox.cds-hooks.org) now supports cards with an error indicator type
Kevin Shekleton (Jan 27 2018 at 19:49):
Every can try it out in our "Card Demo" functionality (click the button in the upper right of the Sandbox)
Robert Sax (Jan 27 2018 at 19:53):
stanson implements order-review (https://staging1-api.stansonhealth.com/07A83F99-BD4A-4DD0-B77C-E59E422F18CB/cds-services)
Grahame Grieve (Jan 27 2018 at 20:22):
thanks
dave olarte (Jan 27 2018 at 20:50):
An example cds-hooks medication-prescribe request body:
{
"hookInstance": "8628592c-b506-4de9-a7b5-1f8b722ee8e6",
"fhirServer": "https://fhir-open.sandboxcerner.com/dstu2/0b8a0111-e8e6-4c26-a91c-5069cbc6b1ca",
"hook": "medication-prescribe",
"redirect": "",
"fhirAuthorization": null,
"user": "Practitioner/example",
"context": [
{
"resourceType": "MedicationOrder",
"id": "0",
"patient": {
"reference": "4342008.000000"
},
"encounter": {
"reference": "4269906.000000"
},
"medicationReference": {
"reference": "",
"display": ""
},
"dosageInstruction": [
{
"timing": {
"code": {
"coding": [
{
"system": "http://hl7.org/fhir/timing-abbreviation",
"code": "QD",
"display": ""
}
]
}
},
"route": {
"coding": [
{
"system": "http://snomed.info/sct",
"code": "26643006",
"display": ""
}
]
},
"doseQuantity": {
"value": 100,
"unit": "mg",
"system": "http://unitsofmeasure.org",
"code": ""
}
}
],
"DISPENSEREQUEST": {
"NUMBEROFREPEATSALLOWED": 0
},
"medicationCodeableConcept": {
"text": "",
"coding": [
{
"display": "",
"system": "http://www.nlm.nih.gov/research/umls/rxnorm",
"code": "1256"
}
]
}
}
],
"patient": "4342008",
"prefetch": {
"patient": {
"response": {
"status": "200 OK"
},
"resource": {
"resourceType": "Patient",
"id": "4342008",
"meta": {
"versionId": "32",
"lastUpdated": "2018-01-12T21:25:43.000Z"
},
"text": {
"status": "generated",
"div": "<div><p><b>Patient</b></p><p><b>Name</b>: SMART, WILMA</p><p><b>DOB</b>: 1947-03-16</p><p><b>Administrative Gender</b>: Female</p><p><b>Marital Status</b>: Married</p><p><b>Status</b>: Active</p></div>"
},
"extension": [
{
"url": "http://fhir.org/guides/argonaut/StructureDefinition/argo-race",
"extension": [
{
"url": "ombCategory",
"valueCoding": {
"system": "http://hl7.org/fhir/v3/Race",
"code": "2054-5",
"display": "Black or African American",
"userSelected": false
}
},
{
"url": "text",
"valueString": "Black or African American"
}
]
},
{
"url": "http://fhir.org/guides/argonaut/StructureDefinition/argo-ethnicity",
"extension": [
{
"url": "ombCategory",
"valueCoding": {
"system": "http://hl7.org/fhir/v3/Ethnicity",
"code": "2186-5",
"display": "Not Hispanic or Latino",
"userSelected": false
}
},
{
"url": "text",
"valueString": "Not Hispanic or Latino"
}
]
}
],
"identifier": [
{
"use": "usual",
"type": {
"coding": [
{
"system": "http://hl7.org/fhir/v2/0203",
"code": "MR",
"display": "Medical record number",
"userSelected": false
}
],
"text": "MRN"
},
"system": "urn:oid:1.1.1.1.1.1",
"value": "10002700",
"period": {
"start": "2016-06-22T20:25:56.000Z"
}
},
{
"use": "usual",
"type": {
"text": "Messaging"
},
"system": "urn:oid:2.16.840.1.113883.3.13.8",
"value": "65DBEC0B8D154E3488FA5FFE9AC7713F",
"period": {
"start": "2017-12-01T16:54:17.000Z"
}
},
{
"use": "usual",
"type": {
"coding": [
{
"system": "http://hl7.org/fhir/v2/0203",
"code": "AN",
"display": "Account number",
"userSelected": false
}
],
"text": "Federated Person Principal"
},
"system": "urn:oid:2.16.840.1.113883.3.13.8",
"value": "9494949494",
"period": {
"start": "2017-09-26T05:00:00.000Z",
"end": "2019-01-02T05:00:00.000Z"
}
},
{
"use": "usual",
"type": {
"coding": [
{
"system": "http://hl7.org/fhir/v2/0203",
"code": "AN",
"display": "Account number",
"userSelected": false
}
],
"text": "Federated Person Principal"
},
"system": "urn:oid:2.16.840.1.113883.3.13.6",
"value": "URN:CERNER:IDENTITY-FEDERATION:REALM:687F29DD-69DD-4DE5-ACB1-FD8A2241EF3A:PRINCIPAL:LQ4SG3D28BY",
"period": {
"start": "2017-09-26T05:00:00.000Z",
"end": "2019-01-02T05:00:00.000Z"
}
},
{
"use": "usual",
"type": {
"coding": [
{
"system": "http://hl7.org/fhir/v2/0203",
"code": "AN",
"display": "Account number",
"userSelected": false
}
],
"text": "Federated Person Principal"
},
"system": "urn:oid:2.16.840.1.113883.3.13.6",
"value": "URN:CERNER:IDENTITY-FEDERATION:REALM:687F29DD-69DD-4DE5-ACB1-FD8A2241EF3A:PRINCIPAL:LQ4SG3D28BR",
"period": {
"start": "2016-11-01T10:00:00.000Z"
}
},
{
"use": "usual",
"type": {
"coding": [
{
"system": "http://hl7.org/fhir/v2/0203",
"code": "AN",
"display": "Account number",
"userSelected": false
}
],
"text": "Federated Person Principal"
},
"system": "urn:oid:2.16.840.1.113883.3.13.6",
"value": "urn:cerner:identity-federation:realm:687f29dd-69dd-4de5-acb1-fd8a2241ef3a:principal:LQ4Sg3D28BR",
"period": {
"start": "2016-11-01T10:00:00.000Z"
}
}
],
"active": true,
"name": [
{
"use": "official",
"text": "SMART, WILMA",
"family": [
"SMART"
],
"given": [
"WILMA"
],
"period": {
"start": "2016-06-22T20:25:58.000Z"
}
},
{
"use": "maiden",
"text": "WILLIAMS,",
"family": [
"WILLIAMS"
],
"period": {
"start": "2017-03-09T19:37:17.000Z"
}
}
],
"telecom": [
{
"system": "phone",
"value": "816-222-2222",
"use": "work",
"period": {
"start": "2017-06-27T17:28:04.000Z"
}
},
{
"system": "phone",
"value": "8168101010",
"use": "home",
"period": {
"start": "2017-02-07T18:56:52.000Z"
}
},
{
"system": "phone",
"value": "913-913-9131",
"use": "mobile",
"period": {
"start": "2017-06-27T17:31:07.000Z"
}
},
{
"system": "email",
"value": "ehanov@cerner.com",
"use": "home",
"period": {
"start": "2017-12-01T16:52:18.000Z"
}
}
],
"gender": "female",
"birthDate": "1947-03-16",
"address": [
{
"use": "home",
"text": "1200 Road\nKansas City, MO 64114\nUSA",
"line": [
"1200 Road"
],
"city": "Kansas City",
"district": "Jackson",
"state": "MO",
"postalCode": "64114",
"country": "USA",
"period": {
"start": "2017-02-07T18:56:52.000Z"
}
}
],
"maritalStatus": {
"coding": [
{
"system": "http://hl7.org/fhir/v3/MaritalStatus",
"code": "M",
"display": "Married",
"userSelected": false
}
],
"text": "Married"
},
"contact": [
{
"relationship": [
{
"text": "Authorized Representative"
}
],
"name": {
"use": "official",
"text": "SMART Jr, FRED RICK",
"family": [
"SMART"
],
"given": [
"FRED",
"RICK"
],
"prefix": [
"Mr"
],
"suffix": [
"Jr"
],
"period": {
"start": "2016-08-31T18:24:54.000Z"
}
},
"t
dave olarte (Jan 27 2018 at 21:51):
The Google spreadsheet which contains Connectathon CDS Service (Discovery) endpoints:
https://bit.ly/cds-hooks-connectathon-tracking
Brett Marquard (Jan 28 2018 at 01:12):
Break out topics! Any suggested breakout topics for tomorrow?
Zach Plata (Jan 28 2018 at 05:31):
General Sandbox update: the /.well-known/jwks.json endpoint is available in the Sandbox, along with the kid field in the JWT to verify against. This means cds services no longer have to use the public key pem file gist we sent out from the Sandbox (this morning) to gain access to the JWT sent to them. Services can just hit that well known endpoint on the sandbox and get all relevant details about the key type, the algorithm, the kid field, etc.
Kalyani Yerra (Jan 28 2018 at 07:14):
My service is available for testing. Please let me know if it working in your EHR.
https://premierclinicalsurveillancefhir.com/CDS_Hooks/cds-services
Dave Carlson (Jan 28 2018 at 13:18):
Are any CDS services supporting 'patient-view' hook and STU3? FHIR version is not indicated in the spreadsheet.
Kevin Shekleton (Jan 28 2018 at 13:34):
@Dave Carlson - With the CDS Hooks Sandbox, you can specify your own FHIR server (say, an HSPC STU3 FHIR server) to test patient-view and STU3.
Grahame Grieve (Jan 28 2018 at 13:35):
I don't follow. the cds-service is also version specific, no?
Kevin Shekleton (Jan 28 2018 at 13:36):
Yes, it is. I mis-read Dave's question as to asking if there are any EHRs which support STU3. However, after re-reading I see he is asking if any CDS Service supports STU3.
Dave Carlson (Jan 28 2018 at 13:39):
Kevin, yes, the only STU3 CDS service I've found so far is, https://oridashiquickhooksstu3.azurewebsites.net/cds
Grahame Grieve (Jan 28 2018 at 14:02):
my server has an /r3 end-point that implements patient-view
Guilherme Del Fiol (Jan 28 2018 at 14:49):
Kevin, yes, the only STU3 CDS service I've found so far is, https://oridashiquickhooksstu3.azurewebsites.net/cds
@Dave Carlson , we support both STU2 and STU3. https://dev-newservice.oib.utah.edu:443/cds-services
Kensaku Kawamoto (Jan 28 2018 at 15:03):
Opioid CDS Hooks endpoint: https://fhir.cygni.cc:8443/opencds-decision-support-service/hooks/cds-services
Sample curl:
curl -v -XPOST -H"Accept: application/json" -H"Content-type: application/json" --upload-file hooks-request4.json https://fhir.cygni.cc:8443/opencds-decision-support-service/hooks/cds-services/opioid-mme
Sample request:
{
"hook": "medication-prescribe",
"hookInstance": "d1577c69-dfbe-44ad-ba6d-3e05e953b2ea",
"fhirServer": "http://localhost:8080/fhir-wrapper/fhirServer",
"user": "Practitioner/phillip",
"patient": "Patient/123",
"context": [
{
"resourceType": "Medication",
"id": "med_id_bup_patch",
"code": {
"coding": [
{
"system": "http://www.nlm.nih.gov/research/umls/rxnorm",
"code": "388508"
}
]
}
},
{
"resourceType": "MedicationOrder",
"id": "medorder_id_bup_patch_draft",
"identifier": [
{
"system": "Order Number",
"value": "1"
}
],
"status": "draft",
"patient": {
"reference": "Patient/123"
},
"medicationCodeableConcept": {
"text": "Buprenorphine patch",
"coding": [
{
"system": "http://www.nlm.nih.gov/research/umls/rxnorm",
"code": "388508"
}
]
},
"dosageInstruction": [
{
"text": "1 patch Transdermal Every 72 hours",
"timing": {
"repeat": {
"boundsPeriod": {
"start": "2018-01-12T00:00:00-06:00"
},
"frequency": 1,
"period": 72,
"periodUnits": "h"
}
},
"asNeededBoolean": false,
"route": {
"text": "Transdermal"
},
"doseQuantity": {
"value": 1,
"unit": "patch"
}
}
],
"dispenseRequest": {
"validityPeriod": {
"start": "2018-01-12T00:00:00-06:00"
},
"numberOfRepeatsAllowed": 0,
"quantity": {
"value": 8,
"unit": "patch"
}
}
}
],
"prefetch": {
"patient": {
"resource": {
"resourceType": "Patient",
"id": "123",
"meta": {
"versionId": "1",
"lastUpdated": "2016-07-06T12:48:01.000+00:00"
},
"text": {
"status": "generated",
"div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <p>Daniel Adams</p>\n </div>"
},
"identifier": [
{
"use": "usual",
"type": {
"coding": [
{
"system": "http://hl7.org/fhir/v2/0203",
"code": "MR",
"display": "Medical record number"
}
],
"text": "Medical record number"
},
"system": "http://hospital.smarthealthit.org",
"value": "1288992"
}
],
"active": true,
"name": [
{
"use": "official",
"family": [
"Adams"
],
"given": [
"Daniel",
"X."
]
}
],
"telecom": [
{
"system": "email",
"value": "daniel.adams@example.com"
}
],
"gender": "male",
"birthDate": "1925-12-23",
"address": [
{
"use": "home",
"line": [
"1 Hill AveApt 14"
],
"city": "Tulsa",
"state": "OK",
"postalCode": "74117",
"country": "USA"
}
]
},
"response": {
"status": "200 OK"
}
}
}
}
Paul Curcio (Jan 28 2018 at 15:38):
I'm getting an "invalid signature" error when attempting to verify the token against the key in the JWKS (both with the jsonwebtoken Node library we're using, and on jwt.io if I just paste it in) ... the key (when turned into PEM) appears to be different between the JWKS and the PEM that was previously provided
Kevin Shekleton (Jan 28 2018 at 15:52):
FYI all - we are having a breakout today at 11am in the Royal Room to discuss how the Connectathon is going, any issues people have run into, changes we've been making to the spec this weekend, and other topics that may come up. I'll make sure to let all of our 4 tables know before we walk over at 11
Martin Tran (Jan 28 2018 at 15:53):
Kevin, yes, the only STU3 CDS service I've found so far is, https://oridashiquickhooksstu3.azurewebsites.net/cds
@Dave Carlson , my cds service supports STU2 and STU3 - https://smart-dev.tsheetsevolved.com/cds-services
Kevin Shekleton (Jan 28 2018 at 15:53):
@Paul Curcio Is this for the Sandbox?
Paul Curcio (Jan 28 2018 at 16:00):
@Kevin Shekleton oh yes, sorry - referring to sandbox.cds-hooks.org/
Kalyani Yerra (Jan 28 2018 at 16:01):
I'm getting an "invalid signature" error when attempting to verify the token against the key in the JWKS (both with the jsonwebtoken Node library we're using, and on jwt.io if I just paste it in) ... the key (when turned into PEM) appears to be different between the JWKS and the PEM that was previously provided
Same error for me too...
Kevin Shekleton (Jan 28 2018 at 16:02):
Tagging @Zach Plata :-)
Zach Plata (Jan 28 2018 at 16:03):
Taking a look after I wrap up this context stuff
Kevin Shekleton (Jan 28 2018 at 16:55):
Reminder: CDS Hooks breakout session in 5 minutes in the Royal Room. I will let all of our 4 tables know before we head over :-)
Kensaku Kawamoto (Jan 28 2018 at 16:56):
(deleted)
Bryn Rhodes (Jan 28 2018 at 20:06):
So does the Cerner test system have the updated context changes? And does it require the security model or can it call an open endpoint still?
Kevin Shekleton (Jan 28 2018 at 20:12):
@Bryn Rhodes - Yes, the Cerner implementation has the context changes and yes we still have the open FHIR endpoint
Bryn Rhodes (Jan 28 2018 at 20:15):
Thanks @Kevin Shekleton
Bryn Rhodes (Jan 28 2018 at 20:22):
Is there an EHR test environment that doesn't have those changes applied yet?
Raj M (Jan 28 2018 at 20:33):
@Zach Plata back tracking from the pem key the jwk should be below as opposed to what is currently in http://sandbox.cds-hooks.org/.well-known/jwks.json {
"kty": "EC",
"use": "sig",
"crv": "P-256",
"kid": "9b4f5be8-055a-408d-9e1a-1af98dcf2509",
"x": "q8Ftr50G2k2OPdge05jBkc6gC12Fq3Y-HyT21lEOty4",
"y": "oqNhGy3GyK2sqCbuFotYQPTq6LMa5UonQ6oXOuCTYDA",
"alg": "ES256"
}
Kevin Shekleton (Jan 28 2018 at 20:53):
Reminder everyone - send me anything you want me to include in our track report out by 3pm today (7min away!)
Guilherme Del Fiol (Jan 28 2018 at 21:06):
Reminder everyone - send me anything you want me to include in our track report out by 3pm today (7min away!)
We tested two CDS services for the Infobutton scenario. Most of the attributes in the Infobutton standard mapped well with CDS Hooks. The main challenges were mapping Atom to CDS Hooks cards, but we found potential solutions. We successfully used prefetch for conditions and the patient resource.
EHRs: We were able to integrate the services with the CDS Hooks Sandbox and Cerner.
// Clinical Knowledge Summary app – returns an app card. The app provides access to summaries of high impact clinical research reports in PubMed.
https://dev-newservice.oib.utah.edu:80/cds-services
// OpenInfobutton - returns two info cards with links to patient education from MedlinePlus and provider reference information from UpToDate
https://dev-newservice.oib.utah.edu:443/cds-services
Zach Plata (Jan 28 2018 at 21:13):
The Sandbox has been updated to point to a newer private key - which should fix some of those invalid signatures some services have been seeing when testing with the JWT.
Bryn Rhodes (Jan 28 2018 at 21:23):
Okay, we updated to the new context, how can we have the Cerner app call our endpoint on Medication-prescribe?
Paul Curcio (Jan 28 2018 at 21:25):
@Travis Cummings - Zach and I noticed that the api.hspconsortium.org open FHIR server doesn't seem to support the "sort" parameter (this is on an Observation call). Do you know if there are any plans to make that work?
Kevin Shekleton (Jan 28 2018 at 21:50):
@Bryn Rhodes - @Matt Henkes can help you
Bryn Rhodes (Jan 28 2018 at 22:03):
Here's the CQF-Ruler endpoint: http://measure.eval.kanvix.com/cqf-ruler/cds-services/cdc-opioid-guidance
Bryn Rhodes (Jan 28 2018 at 22:03):
{
"hookInstance": "d1577c69-dfbe-44ad-ba6d-3e05e953b2ea",
"fhirServer": "https://sb-fhir-dstu2.smarthealthit.org/smartdstu2/open",
"hook": "medication-prescribe",
"user": "Practitioner/example",
"context":
{
"resourceType": "MedicationOrder",
"id": "medrx001",
"dateWritten": "2017-05-05",
"status": "draft",
"patient": {
"reference": "Patient/Patient-12214"
},
"medicationCodeableConcept": {
"coding": [
{
"system": "http://www.nlm.nih.gov/research/umls/rxnorm",
"code": "197696"
}
]
},
"dosageInstruction": [
{
"text": "Take 40mg three times daily",
"timing": {
"repeat": {
"frequency": 3,
"frequencyMax": 3,
"period": 1,
"periodUnits": "d"
}
},
"asNeededBoolean": false,
"doseQuantity": {
"value": 40,
"unit": "mg",
"system": "http://unitsofmeasure.org",
"code": "mg"
}
}
],
"dispenseRequest": {
"quantity": {
"value": 3000,
"unit": "mg",
"system": "http://unitsofmeasure.org",
"code": "mg"
}
}
},
"patient": "Patient/Patient-12214",
"prefetch": {
"medication": {
"resource": {
"resourceType": "Bundle",
"entry": [
{
"fullUrl": "https://sb-fhir-dstu2.smarthealthit.org/smartdstu2/open/MedicationOrder/medrx002",
"resource": {
"resourceType": "MedicationOrder",
"id": "medrx002",
"meta": {
"versionId": "1",
"lastUpdated": "2017-10-21T20:55:38.000+00:00"
},
"dateWritten": "2017-04-25",
"status": "active",
"patient": {
"reference": "Patient/Patient-12214"
},
"medicationCodeableConcept": {
"coding": [
{
"system": "http://www.nlm.nih.gov/research/umls/rxnorm",
"code": "199789"
}
]
},
"dosageInstruction": [
{
"text": "Take 50mg twice daily",
"timing": {
"repeat": {
"frequency": 2,
"period": 1,
"periodUnits": "d"
}
},
"asNeededBoolean": false,
"doseQuantity": {
"value": 55,
"unit": "mg",
"system": "http://unitsofmeasure.org",
"code": "mg"
}
}
],
"dispenseRequest": {
"quantity": {
"value": 3000,
"unit": "mg",
"system": "http://unitsofmeasure.org",
"code": "mg"
}
}
}
}
]
}
}
}
}
Travis Cummings (Jan 29 2018 at 04:57):
Hi @Paul Curcio The HSPC API servers all are running versions of the HAPI FHIR server and should support the sort operation. Could you give me an example of sort not working (with the full URL)?
Paul Curcio (Jan 29 2018 at 15:29):
Turns out we were using the wrong syntax ("sort" instead of "_sort", among other problems). Fixed that up and it's working now - thank you!
Dave Carlson (Jan 31 2018 at 03:34):
@Guilherme Del Fiol I am attempting to test your OpenInfoButton service and get a 500 error with server Null Pointer Exception. Suspect it's because I am sending STU3 data and your server expects DSTU2? Any plans to support STU3? Would love to test the info button services! Thanks.
Guilherme Del Fiol (Jan 31 2018 at 22:14):
@Guilherme Del Fiol I am attempting to test your OpenInfoButton service and get a 500 error with server Null Pointer Exception. Suspect it's because I am sending STU3 data and your server expects DSTU2? Any plans to support STU3? Would love to test the info button services! Thanks.
We had to change the port that the services are running on. Which one are you using? We have two different services:
1) Only works with STU2 - although it works with STU3 data, the prefetch uses a sort that is STU2-specific: https://dev-newservice.oib.utah.edu:443/cds-services
2) This one should be STU-agnostic - https://dev-newservice.oib.utah.edu:80/cds-services
Let me know if it still doesn't work.
Last updated: Apr 12 2022 at 19:14 UTC
