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."
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, firstname.lastname@example.org
- 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.
Server Implementers: Epic, Cerner, Meditech
Server implementers and clients are both welcome.
A codelab tutorial is being developed at https://aka.ms/patient-lists-codelab 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 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.
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).
FHIR Server includes additional "columns" in patient list
Action: FHIR Server returns Group resource with an extension referencing a Questionnaire resource, and an extension referencing a QuestionnaireResponse resource per patient
Precondition: A group is defined in a provided FHIR Server in such a way that any participant can read it. Questionnaire exists which defines additional list columns.
Success Criteria: The client parses extensions.
Bonus point: Client validates questionnaireresponses against questionnaire.