Planlagte endringer for Basis-API versjon 3.x
Nedenfor listes implementerte og planlagte endringer på Basis APIet som potensielt kan påvirke konsumentløsninger.
Listen nedenfor oppsummerer API-endringer som er "Breaking" eller "Behavior”. Her er det viktig at leverandørene verifiserer og tester grundig, og sikrer eventuelle nødvendige justeringer. I tillegg er enkelte saker også markert med “New-feature“, dette er tilleggsinformasjon som ikke påvirker eksisterende løsning, men hvor det vil kreve tilpasninger når man velger å ta i bruk funksjonaliteten.
Detaljer skal være oppdatert i Simplifier.
Apr 4, 2024 Planlagte Endringer i 3.10 og 3.11, basert på tall fra 04.04.24
Jira-nr | Summary | Fix versions | Labels | What's New Text (aka Release Notes) |
|---|---|---|---|---|
Map discontinuation information from M5s within getMedication responses - Basis API |
| |||
Errors in sendMedication for when lookup was done on old PID | Updated GetMedication to use the new Pid in the medication bundle when the Pid in the request is old, so when we run the sendMedication it does not give an error. | |||
SFM allows sendMed with invalid PLL-id, but then this fails in the following getMedication | Defect BasisAPI SFM shall tolerate incoming PLL with a PLL-id not being a UUID | |||
| Internal issue. Related to validation between incoming and outgoing bundles in Basis | |||
Improved logs for the support team. Will indicate the reason for unsuccessful access. | ||||
Evaluate SFM-9572 specification for mapping of discontinuation date | This issue improves the detection of "midnight" in translation between e-resept messages and SFM, including different variations in timezones. | |||
EO1007/2020 Include discontinuation information within M5 - Basis API | Now when a user does a sendMedication and includes discontinuation in a medication that has recall info, the discontinuation data will be included in the M5 sent | |||
As the Basis API I want proper error handling when attempting to forward messages from RF |
| A cronjob scheduler was implemented to run every 2 minutes (Configurable). Every step is logged. Database queries supplied in comment for updating retryCount and state for messages, to be able to keep on or stop trying to forward them. | ||
AS Multidose doctor using Helseplattformen I want to do sendMedication without createPLL=true |
| Solves the requested non-standard multidose behaviour by Helseplattformen (MD doctor can do updates without sending M25.1) | ||
Defect, will probably be included in 3.10 | ||||
Defect, will probably be included in 3.10 | ||||
GET Task for base-fhir does not work without timezone information |
| Defect This might be a breaking change if vendors have previously sent timestamp without timezone information, adding the APIChange-Breaking label to be sure. | ||
Defect SFM inkluderer nå med refusjonskode for papirresepter i getMedication | ||||
Questions from M25.2 are not included in getMed if a M25.3 has been sent afterwards | Defect Fikset en feil der spørsmål ikke ble returnert selv om de var ubesvart dersom det hadde kommet en M25.3 fra MD-apotek | |||
Basis API / GetMedication returns confusing recallstatus=false | Defect | |||
Updated the medication bundle in the get medication method, to return the special case where there are no m25 messages but there is a multidose pharmacy or doctor, where now it will return the information in the m9.12 in the pll info section. Added to the list Apr 5, 2024 | ||||
|
|
|
|
|
Dec 18, 2023 Nå skal ny versjon av 3.9 være tilgjengelig i test3 og test4.
Jira-nr | Summary | Fix versions | Labels | What's New Text (aka Release Notes) |
|---|---|---|---|---|
getMedication will return one sfm-PLLinfo record for each M25.x message from RF/KJ. Affects "multidose" patients. Detailed info will be presented in simplifier | ||||
Validation for sendmedication is now done by fetching the latest GetMedicationBundle that has a value in the RfLookupTime column and comparing the compositionIdentifier. This essentially filters out any getmedications performed by nurses. As before the if the latest medicationBundle is from a sendMedication, that will still be picked up and validated against. What changes here is that a doctor can send sendMedication over and over again after doing an initial getMedication even if a nurse does a getMedication in the mean time. The threshold for a valid getmedication still applies and is validated against. The doctor will need to do a new getmed if the time since his last getmed passes over the valid threshold. | ||||
BaseFhir task endpoint is now accepting organization tokens without any user information | ||||
SFM shall use the latest version of M9.11 against RF, and receive latest version of M9.12 | Updated info from RF on multidose responsibility, including necessary id's for pharmacy. | |||
Improved multidose. Related to SFM-17745 | ||||
Rettet en feil i url som mottas i retur ved søk i FHIR-API | ||||
Rettet en feil der en oppdatering av organisasjon som manglet sfm-id fjernet en linje i ClientIdentities tabellen | ||||
Unnecesary warnings/errors to end user will be avoided by this improvement. No implementation changes required. | ||||
Invalid Magistrell medication is causing an error during sendMedication |
| SFM returnerer nå en bedre feilmelding dersom sendMedication for en magistrell forskrivning mangler mengde eller navn | ||
| SFM will now reject organization create and update with wihte-space in identifier strings (note that this was accepted, but caused problems, hence a NA change) | |||
AllergyIntolerance in getMedication does not include <Atc> element in <Legemiddelreaksjon> | Fixed according to specification. | |||
reseptdate not included in getMed for recalled resepts when KJ lookup is done |
| Reseptdate is included when KJ lookup is done | ||
| Extended control due to complexity issues | |||
As SFM Basis I want to reject $sendMedication from MD doctor where createPLL is not true |
| Extended control due to complexity issues | ||
No validation error is returned when recalling the same bandaprescription twice in sendMedication | 400 validation error is returned if such case occur | |||
As an EPJ I do not want the SFM to reject diagnosis codes that the SFM does not already know | SFM vil nå kunne motta diagnosekoder fra forskjellige kodeverk selv om SFM ikke kjenner kodeverket fra tidligere | |||
[API] sfm-Practitioner and sfm-Person resources are limited to 10 results | sfm-Practitioner and sfm-Person resource search in Datashare now returns number of matches according to FHIR spec | |||
SFM will now support flow of MedicationStatement/dosage/additionalInstruction to and from EPJ in $getMedication and $sendMedication using the new fields in the extended M1 and M25.1 messages. Note: cardinality rules are more specfic than the profile indicates | ||||
As a security champion I would suggest reviewing the validation of M25.1 messages sent | SFM er utvidet med skjemavalidering for M25.1 meldinger | |||
| Updated version of following profiles included:
https://simplifier.net/R4Medication/SfmAdministrering
https://simplifier.net/R4Medication/SfmBandaPrescription
Note: Forge tool implies some cardinality changes from omitted/implicit to explicit when updating profiles. | |||
AS an EPJ I want the FHIR "bundle.total" parameter to be correctly set when searching | Corrected search response Bundle.total according to FHIR specification | |||
As the Basis API I do not want to try to send the same M1 multiple times to RF | Unnecesary warnings/errors to end user will be avoided by this improvement. No implementation changes required. | |||
[API] Calling sendMedication with a missing medicationStatement results in a 500 error | This is a fix: The sendMedication without medication statement return correct error message. | |||
[API] M25.1 gets rejected due to invalid RefToParent when two sendMedications are sent succesively | This is a fix: Succesive sendMedications behaves in a correct manner from SFM to RF | |||
New content in sfm-lib-list to support detailed dosing | ||||
As the SFM I want to use renewal information in an updated M9.6 to link renewed resepter |
| $getMedication now returns linked prescriptions in a chain as specified even when a lookup in KJ is not available. | ||
| When extension in received M1 or M25.1 is avalable, The following mapping applies to sfm-MedicationStatement: | |||
$sendMedication now includes information from dosage text and dosage additional instructions in M1 and M25.1 message extensions. | ||||
As the Basis API I want proper error handling when attempting to forward messages from RF |
| A cronjob scheduler was implemented to run every 2 minutes (Configurable). Every step is logged. Database queries supplied in comment for updating retryCount and state for messages, to be able to keep on or stop trying to forward them. | ||
| SFM will ensure updated information about Multidose responsible pharmacy in getMedication for multidose patients. | |||
The use of stopdate as timedate in sfm-discontinuation in getMedication is not correct |
| Rettet en feil på format på seponeringsdato i Basis API Added to the list: Apr 5, 2024 |