Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Track overview

Short Description

One of the 2020 Argonaut projects is Patient Lists, which enables a standardized way for software to access lists of patients which are commonly used in an EHR setting.  For example, "all patients in a location" or "all the patients on my schedule today."

Long Description

Gather early feedback from implementers on the Argonaut Patient Lists project.


  • Test the design of a Resource/set of Resources
  • Test an Implementation Guide
  • Test a FHIR-associated specification
  • Educate on the use of a FHIR technology/IG

Submitting Work Group/Project/Accelerator/Affiliate/Implementer Group


Proposed Track Lead

Carl Anderson,

Related tracks


FHIR Version

  • Current build

Specification(s) this track uses

Artifacts of focus

Clinical input requested (if any)

We're running with a handful of example patient lists, such as "all the patients in a location" and "all the patients a provider will see in a day / week" - but if there are other more relevant lists, suggestions from clinicians are welcome.

Patient input requested (if any)

Same as above - if there are any well established places where lists of patients are frequently used or useful, patient/caretaker input is welcome.

Expected participants

Server Implementers: Epic, Cerner, Meditech

Zulip stream

Track Orientation


Track details

System Roles

Server implementers and clients are both welcome.
A codelab tutorial is being developed at that will be a good starting point for software developers.  Relevant resources for server developers will also be linked-to from the codelab, so it should be a good starting point for all participants.

Server Developers


Server Passes Capability Checks

Action: An open source tool examines a participant server, confirming that it advertises capabilities correctly and passes a simple smoke test.

Precondition: A group is defined in the participant server in such a way that the smoke test will pass (details TBD).

Success Criteria: The server capabilities suggest patient lists are supported and the smoke test passes.

Bonus point:

Client Software Developers


Software Displays an Example Patient List from FHIR Server

Action: Participant is able to connect to a FHIR Server and retrieve a patient list, rendering it in their app.

Precondition: A group is defined in a provided FHIR Server in such a way that any participant can read it.

Success Criteria: The client renders the complete patient list.

Bonus point: Correct pagination is handled, as well as any other relevant details that may need to be gathered by invoking other queries against the server (for example, data related to the most recent encounter).


The test scripts for server developers are still a work in progress, but the clients developers can configure their software to connect to a provided FHIR Server.

Security and Privacy Considerations


  • No labels