FHIR Chat · docs / PR #385 link to MedRequest, not MedOrder

Stream: cds hooks/committers

Topic: docs / PR #385 link to MedRequest, not MedOrder

Github Notifications (Aug 02 2018 at 04:10):

isaacvetter opened PR #385
from iss308-fix-link-to-MedRequest to master

Fixes #308.
The issue is that the link to FHIR's MedicationOrder resource no longer resolved. This is because from DSTU2->STU3, FHIR changed the name of this resource from MedicationOrder to MedicationRequest. Instead of pointing to the DSTU2 MedicationOrder resource, I updated the example and link to point to MedicationRequest.

Github Notifications (Aug 02 2018 at 04:10):

isaacvetter review_requested PR #385

Github Notifications (Aug 02 2018 at 04:10):

isaacvetter review_requested PR #385

Github Notifications (Aug 02 2018 at 04:10):

isaacvetter review_requested PR #385

Github Notifications (Aug 08 2018 at 13:43):

kpshek synchronized PR #385

Github Notifications (Aug 08 2018 at 15:12):

kensaku-kawamoto commented on PR #385

Should there be a generic hook definition, and ones specific to FHIR versions if needed? E.g., medication-prescribe with MedicationOrder for FHIR versions XYZ, MedicationRequest for FHIR versions ABC.

Github Notifications (Aug 08 2018 at 15:22):

kpshek commented on PR #385

Should there be a generic hook definition, and ones specific to FHIR versions if needed? E.g., medication-prescribe with MedicationOrder for FHIR versions XYZ, MedicationRequest for FHIR versions ABC.

This is exactly what we document for hook authors already -- to specify any differences/particulars for each FHIR version that is in use. You can see this in our existing documentation for the medication-prescribe hoook.

The question is regarding the _specification_ documentation that references the medication-prescribe hook as an example in the context field documentation. If we simply referenced the patient-view hook in the example instead, we avert the complexities of various FHIR versions here.