--- tags: 2022 --- # Argo 22: Patient-access Brands and Endpoints See migrated content at https://build.fhir.org/ig/HL7/smart-app-launch/brands.html.
Last changed by  
 
Argonaut
2369

Read more

Bulk Export Parameter Processing Flow

flowchart TB all[All resources available for Bulk Export] group["Exclude resources for patients not in group\n(if group export)"] authz["Exclude unauthorized resources\n(based on scopes and user)"] type["Exclude resources with types not listed in `_type` parameter\n(if provided/supported)"] since["Exclude resources updated before `_since` timestamp\n(if provided/supported)"] typefilter_criteria[Resource types that have _typeFilter criteria] typefilter_filter[Exclude resources that don't meet the criteria\nin at least one of the criteria sets] typefilter_no_criteria[Resource types that don't have _typeFilter criteria] typefilter_no_filter[Retain all resources for these resource types]

5/6/2024
Bulk Optimize Notes

Improve

3/18/2024
FHIR Bulk Match Operation

Request URL: [base]/Patient/$bulk-match

2/20/2024
Argo 23 - FHIR Vitals Write

Provider direct writeProvider uses a SMART-on-FHIR app with a [patient|user]/Observation.c scope to save vital sign Observation into an EHR during a patient visit or a SMART Backend Services app with a [system]/Observation.c saves Observation resources into an EHR on a provider’s behalf. The Observation resource follows the appropriate US Core vital sign profile. For example, a blood pressure cuff sends readings to an standalone launch SMART-on-FHIR app on a practice tablet that a clinical user then uses to write the data to a patient’s record in the EHR.

10/31/2023
Read more from Argonaut
Published on HackMD