Structured - Meds are being returned based on the Last Issue Date and not the End Date about gpconnect-demonstrator HOT 5 CLOSED

See acute meds for last 12 months for patient 2 Mike Meakin
There is a medication (Tramadol 5-0mg capsules) with a start date of 26/4/2018 not end dated so this is classified as current.

from gpconnect-demonstrator.

See email from 14/7/2021 from MH which refers to 1.2.7

from gpconnect-demonstrator.

I have deleted confusing 0.7 comments that actually refer to #372

from gpconnect-demonstrator.

MH Email:

Done a few requests in the swagger and it looks to me like the filtering is against the last issued date extension on the medicationStatement (or something which holds the same date as that).

Looking at Sertraline it has the following

{
  "resource": {
    "resourceType": "MedicationStatement",
    "id": "1",
    "meta": {
      "profile": [
        https://fhir.nhs.uk/STU3/StructureDefinition/CareConnect-GPC-MedicationStatement-1
      ]
    },
    "extension": [
      {
        "url": https://fhir.nhs.uk/STU3/StructureDefinition/Extension-CareConnect-GPC-MedicationStatementLastIssueDate-1,
        "valueDateTime": "2018-08-17"

That same element for Lantus is 27/8 and it is 29/8 for the other three meds.

Search date of 17/8 returns all meds
Search date of 18/8 returns four meds (sertraline missing)
Search date of 27/8 as above
Search date of 28/8 returns 3 meds (lantus is not missing)
Search date of 29/8 as above
Search date of 30/8 no meds

So consumer can search by date and get different meds back as a result, but it probably doesn’t conform to the actual spec detail of the search criteria as Medicus have pointed out (there are other issues with the data too, such as active meds with end dates)

from gpconnect-demonstrator.

Amended to just check start and end dates not last issued etc
Monthly autoincrement of meds dates now implemented

from gpconnect-demonstrator.