Update the Quick Start Documentation

[c-schuler]

This purpose of this task is to walk through the Quick Start guide in the IG and update links, content (artifacts, request/response, etc) and workflows. This issue is relevant for both the master (2022) and 2016 branches.

Pull request 2022: https://github.com/cqframework/opioid-cds-r4/pull/336 Pull request 2016: https://github.com/cqframework/opioid-cds-r4/pull/337

[alackerbauer]

• [x] remove cqf-ruler-r4 from all URLs in http://build.fhir.org/ig/cqframework/opioid-cds-r4/quick-start.html#cds-hooks-service to comply with the basic setup described for docker ect in the cqframework , e.g. http://localhost:8080/fhir/Library or http://localhost:8080/cds-services
• [x] add link to 'opioidcds-rec10-patientview-bundle' in http://build.fhir.org/ig/cqframework/opioid-cds-r4/quick-start.html#loading-content
• [x] 404 for bundle ​opioidcds-10-patient-view-bundle (putting single resources instead), e.g. PUT http://localhost:8080/fhir/PlanDefinition/opioidcds-10-patient-viewand no bundle for all terminologies exist - want to avoid PUTTing them separately: http://build.fhir.org/ig/cqframework/opioid-cds-r4/terminology.html --> the bundle to use that includes all resources plus terminology can be found here: bundles/rec-10/opioidcds-10-patient-view-bundle.json
• [x] after loading all resources that are listed, including all ValueSets, the cds-services remain empty work after a restart / some time that has passed.
• [x] CDS sandbox connections is failing --> this was an issure due CORS settings and worked in a browser that is ignoring CORS.

[1anja1]

• [ ] quickstart-medications-bundle (test data) is also missing - add link to this bundle here http://build.fhir.org/ig/cqframework/opioid-cds-r4/quick-start.html#loading-content

[1anja1]

• [ ] "from the request-example-rec-10-patient-view-illicit-drugs.json file above" in section http://build.fhir.org/ig/cqframework/opioid-cds-r4/quick-start.html#cds-hooks-sandbox - this file does not exist in the quickstart - considering replacing with request-example-rec-10-patient-view-no-screenings.json
• [ ] match all mentions of the patient to the correct id

For me the CDS sandbox worked up until the point where it cannot find the patient

The patient exists though:

[1anja1]

I updated the 2022 quick start guide with all changes except the links to the bundles - (responses need to be checked once the correct bundles are available) The changes can be found in this branch: #335-update-quick-start-documentation

[alackerbauer]

@1anja1 the thing you describe about not being able to switch the patient might be an actual bug in the sandbox. All GET requests go through and are successful (status code 200) - just the JS code has some problem since it is expecting something else in the bundle, and/or our setup for this scenario is not properly providing everything that is expected: of note, the conditions of our patients are empty, or better said: there is no single condition on the server.

--> solved by making sure the patient has a name element (see comment below)

[alackerbauer]

do you have any idea where the quickstart-medications-bundle could be found? i searched through different tags but also in older versions it seems to not be existent.

can't find that bundle, created a new bundle with the MedicationRequest resources originating from this bundle: request for the rec 10 patient view.

[1anja1]

all bundles and links in the 2022 version are now updated (on the branch for this ticket), however, when executing all the statements as described in the guide the cards response does not contain the suggestions element like it was shown in the old version of the quickstart guide Current:

Old version:

[alackerbauer]

@1anja1 I went through the new guide and it is looking good in general. some things I have discovered:

• cds sandbox: the patient switching only works when our sample patient has a name element. if you experience the same behaviour, we should add such element to the quickstart sample patient
• in the last part, for testing the service in the cds sandbox, the ID in the URL of the PUT request is different from the ID element in the Patient resource. they need to be the same ID
• I experience the same issue with no suggestions showing in the response cards, ~which I believe is not expected behavior. we will ask for some clarification on what the expected behaviour is and where the problems are.~ --> see comment below

[1anja1]

all bundles and links in the 2022 version are now updated (on the branch for this ticket), however, when executing all the statements as described in the guide the cards response does not contain the suggestions element like it was shown in the old version of the quickstart guide Current:

Old version:

The card we are getting might actually be the expected behaviour. It is the same as the response in this File: https://github.com/cqframework/opioid-cds-r4/blob/31916c12adeaf2f3dece330910e0f06d896340e5/input/pagecontent/responses/OpioidCDSREC10PatientView/response-example-rec-10-patient-view-no-screenings.json

[alackerbauer]

finished 2016 including comments of last stand up meeting. still need to pull in changes for 2022.