Skip to content

Design MPI API #155

@ericbuckley

Description

@ericbuckley

Summary

Add and amend the existing MPI API endpoints to wholistically address a wide variety of MPI management use cases.

Acceptance Criteria

  • A list of use cases for when and why an upstream user would want to adjust the MPI
  • A proposal for a new set of API endpoints to manage the MPI

Background / Context

Record Linker was initially designed to address the automatic loading and organizing patient documents from upstream providers (hospitals, clinics, labs, etc). While this is a very important use case to cover, its not the only source of information that an MPI should be able to track. There are many use cases in which the downstream users, case investigators and epidemiologists, want to manually adjust the MPI based on information they've acquired post document ingestion.

A few additional endpoints have been added to help address some of these use cases, however they don't address all the use cases. Let's revisit these, and the use cases that are necessary for upstream users, to create a new, complete set of API endpoints to manage the MPI data.

Metadata

Metadata

Assignees

Labels

spikeResearch or investigation into a technical issue

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions