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

Argonaut FHIR R4 using US Core

Short Description

This track will test US FHIR Core IG 3.1.1 

Long Description

The US Core Implementation Guide version 3.1.1 which is based on FHIR R4 is the basis for further testing and guidance by the Argonaut Project Team. The guide will retain the US Core artifacts and names and provide additional content and guidance specific to Data Query Access for purpose of ONC Certification testing  § 170.315(g)(10) of the servers for conformance to the profiles and be capable of responding to all of the “supported searches” specified in the US Core Implementation Guide Server CapabilityStatement.

Connectathon Schedule

Whova Link:

Signup sheet:

September 10th (Thursday) 9:30 AM ETTrack Kick Off

10:00 AM ETInferno Q&A

2:00 PM ETUS Core Moving Forward
September 11th (Friday)1:00 PE ETTrack final discussion

Orientation planned for Tuesday 9/1/2020 at 12 PM EDT!

Orientation Presentation


  • Testing an implementation Guide

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

  • Argonaut

Proposed Track Lead

  • Yunwei Wang
  • Brett Marquard

Related tracks


FHIR Version

  • 4.0.1

Specification(s) this track uses

Artifacts of focus

  • US Core profiles and guidelines required by ONC Rules

Clinical input requested (if any)


Patient input requested (if any)


Expected participants

  • Server
    • Cerner
    • Epic
    • Inferno (reference server)
    • ???
  • Client
    • Inferno (program edition)
    • Touchstone
    • ???

Zulip stream



Scenario 0: Demonstrate support authentication and authorization 

  • Read Server's capability statement to decide if server requires authentication
  • If server requires authentication
    • Follow SMART App Launch IG to start client

Scenario 1: Patient search

  • Searches by _id
  • Searches by identifier
  • Searches by name
  • Searches by gender + name
  • Searches by birthdate + name
  • Bonus: Searches by _id + _revIncludes: Provenance:target
  • Validate search result

Scenario 2: Smoking Status search

  • Searches by patient + code
  • Bonus: Searches by patient + code + _revInclude: Provenance:target
  • Validate search result

Scenario 3: Clinical Notes search

  • Searches DocumentReference by patient + type
  • Searches DiagnsoticReport by patient + category
  • Validate DiagnosticReport and DocumentReference reference the same attachment

Scenario 4: Provenance Search

  • Search Patient by _id + _revIncludes: Provenance:target (if not done in Scenario 1)
  • Search Smoking Statue by  patient + code + _revInclude: Provenance:target (if not done in Scenario 2)
  • Bonus: Test retrieving, editing and posting an update

Scenario 5: Search and validate additional resources using client application

  • validate searches from each Profile Quick start are supported, resources retrieved as search results are valid. 
  • The list of candidate resource profiles are listed at the end of this page.

Scenario 6: End-to-End § 170.315(g)(10) Test

  • Run all § 170.315(g)(10) required tests

Scenario 7: Bonus: Writing 

  • Create DocumentationReference

Security and Privacy Considerations


Open discussion items

  • Process for adding new profiles to US Core
  • Release cycle for US Core
  • Future profiles to consider for Argonaut and US Core. 
    • Reminder: US core is the foundational IG for clinical data. Expansion of new elements is dependent on broad acceptance of data elements/classes. See proposed growth approach in Future of US Core

* Test the servers for conformance to the US Core profiles required by USCDI, ONC Standardized API for Patient and Population Services criterion § 170.315(g)(10) in the 2015 Edition Cures Update, and beyond! Here is list of profiles:

  • US Core AllergyIntolerance Profile
  • US Core CarePlan Profile
  • US Core CareTeam Profile
  • US Core Condition Profile
  • US Core DiagnosticReport Profile for Laboratory Results Reporting
  • US Core DiagnosticReport Profile for Report and Note exchange
  • US Core DocumentReference Profile
  • US Core Encounter Profile
  • US Core Goal Profile
  • US Core Immunization Profile
  • US Core Implantable Device Profile
  • US Core Laboratory Result Observation Profile
  • US Core MedicationRequest Profile
  • US Core Organization Profile
  • US Core Patient Profile
  • US Core Pediatric BMI for Age Observation Profile
  • US Core Pediatric Weight for Height Observation Profile
  • US Core Practitioner Profile
  • US Core Procedure Profile
  • US Core Provenance Profile
  • US Core Pulse Oximetry Profile
  • US Core Smoking Status Observation Profile
  • FHIR Blood Pressure Profile
  • FHIR Body Height Profile
  • FHIR Body Temperature Profile
  • FHIR Body Weight Profile
  • FHIR Head Circumference Profile
  • FHIR Heart Rate Profile
  • FHIR Respiration Rate Profile

Track Report


The goal for this track is to test and discuss US Core v3.1.1

List of participants 

  • Allscripts: Emma Jones
  • Cerner: Drew Torres
  • Dynamic Health IT: Matthew Davis, Ozlem Kurt, Raychelle Fernandez 
  • GE Healthcare: Abderrazek Boufahja
  • Mathematica: Llew Brown
  • MaxMD: Keith Finlay
  • MITRE: Rob Scanlon, Yunwei Wang
  • ONC: John Bender, Matt Rahn
  • WaveOne Associate: Brett Marquard
  • Yale: Elizabeth Drye

Systems which have implemented the IG, Profile, or Resource, and approximate percentage covered

  • Dynamic FHIR
  • GE Healthcare
  • Inferno

Notable achievements

  • Outlined a plan for resolving Must Support in US Core
  • Provided overview and basic testing from inferno and Postman and a few servers
  • Presented proposed US Core release cycle - positive feedback

Screenshots if relevant and interesting and/or links to further information about implementations/achievements

Discovered issues / questions (if there are any)

  • FHIR Validator/Publisher interaction with US Core Must Support - disallowing references and data types if not noted
  • Certain FHIR servers are still adding search paramater support
  • Device question to FDA on use of the carrierHRF vs carrierAIDC - confirm systems only support one.

Next steps

  • (Yunwei/Brett) Schedule time on FHIR-I to review FHIR Validator/Publisher with US Core - post the time in Argonaut zulip
  • (Brett) Develop a google form on MS/Element choices (may come post WGM).
  • (Brett) Formalize with CGP/Eric/HL7 JIRA issue review and ballot plan - Thursday 2-330 PM WGM. 
  • (Ozlem) Device question to FDA on use of the carrierHRF vs carrierAIDC - confirm systems only support one. Report answer on Argonaut Zulip channel. 

  • No labels