Development update – May 2021

Welcome to the next instalment of our upcoming development blog. Our focus this month is:

  • Allowing existing patients to be added to new teams, including to teams in an org they were not part of previously, via the HL7 API 
  • Adding COVID-19 tests to the Tests page
  • Improving the display of measurements from devices so that the units are easier to interpret 

HL7 API – Adding patients to teams update

We are expanding our HL7 API functionality to allow institutions to add patients to teams via HL7 when they are updating patient records (our existing API only supports adding patients to a team when their records are being created). 

Institutions will be able to add patients to teams by adding the alias for the appropriate team(s) in the ZTM segment of A28 and A31 messages. This will allow patients to get immediate access to the team’s resources, including library links, care plan templates, consultation questionnaires and messaging contacts. Read more about this here.

Tests for COVID-19 and renal conditions

We will support three new COVID-19 tests:

  1. COVID-19 antigen lateral flow test (respiratory swab)
  2. COVID-19 RNA PCR test (respiratory swab)
  3. COVID-19 IgG+IgM antibodies rapid test (blood)

We are adding these so that patients and their caregivers can record the results of these tests in a patient’s record. This is particularly useful when a patient is performing these tests themselves at home. 

We will also be adding tests for renal conditions in the following groups: 

  1. Tests after dialysis session
  2. Tests for kidney dialysis
  3. Organ transplant tests
  4. Purine and Pyrimidine tests
  5. Protein electrophoresis urinalysis
  6. Dialysis adequacy tests
  7. Pancreas function tests
  8. Ciclosporin (Cyclosporine) levels
  9. Protein electrophoresis urinalysis
  10. Thiopurine methyltransferase activity

Displaying more meaningful data from devices

We will be updating some measurements so that they are displayed in meaningful units to help users interpret the information easily. These updates will include: 

  • Converting sleep from seconds and displaying it in hours & minutes 
  • Converting activity (running etc) from meters and seconds into km & minutes 
  • Updating the graphs so that this these measurements are easier to interpret by adding appropriate indexes and starting the Y axis at 0 
  • Adding these new units to the ‘Add measurement’ screen so users can enter these measurements in this format too

GET /v2-beta/measurements/{patientId} to return all measurements

Currently, the GET /v2-beta/measurements/{patientId} API can only be used to retrieve one measurement type: medication compliance. We will soon allow any supported measurement to be retrieved.

FHIR API Patient search will support local organisation identifiers and PKB identifiers

In the coming months, we are going to expand our FHIR API Patient resource so that it will be possible to search for patients using a local organisation identifier or PKB identifier. Currently, Patient search is only possible using a national identifier. 

This month, we’ll start work on the existing FHIR NamingSystem type search to allow a System caller to execute a search. This will allow a System caller to determine what identifier system to provide as input to a Patient search when searching using a local organisation identifier.

Continued work from April

We will continue to work on the following features this month. Please see our previous blogs for more information:

  1. Restarting EMIS extract service
  2. Improving our registration forms. 

This blog describes the features we are working on that we hope to release over the next few weeks. To learn more about other features that our developers are currently working on, please visit our roadmap.

We’ll be back next month with another update on the improvements we’re making for you. In the meantime, if you have any feedback we’d love to hear from you.

Leave a Reply