IHE / pharm-meow

IHE Pharmacy Medication Record Profile Implementation Guide
MIT License
2 stars 0 forks source link

FHIR resources and their role in this context #2

Open rlindstrm opened 1 year ago

rlindstrm commented 1 year ago

MedicationStatement MedicationRequest MedicationDispense MedicationAdministration? Medication CarePlan (mentioned, but out of scope?) ...

rlindstrm commented 1 year ago

Estonian draft on this CarePlan we consider to be out of scope. From our side, the clinical workflows are still on CDA, and the CarePlan would at best be an artificial extra that actually is not used in a workflow.

rlindstrm commented 1 year ago

Related to #5

rlindstrm commented 10 months ago

https://chat.fhir.org/#narrow/stream/179249-Medication/topic/MedicationOverview.20-.20Document.20Bundle.20or.20List

costateixeira commented 10 months ago

We will consider but not enforce the use of documents or Lists. There should be a section in the IG showing when to use one or the other, and the impact this has. The "core" of the profile is the ability to express the medication lines in a consistent way across all these types of presentation and their rules (i.e. "above" prescriptions and dispenses). This would be an option in IHE:

We will use only a PULL mechanism.

Options:

  1. Document: The transaction would be "Retrieve document":
  2. List: The transaction would mean "Get me the treatment lines for this patient" : GET List?type=Medication or GET MedicationStatement?_list=List001
  3. Not for foreground IHE transaction: "Raw" get the resources GET MedicationStatement