Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Refer to individual Server implementation details in the Sprint Tracker! Spreadsheet.


Report Out

2020-01 US Core


Postman Collection connected with Cerner Sandbox.  

  • planning to maintain the Collection and share.
  • add Visualizer


  • Tested with Epic - update for easier connecting
    •  Still requiring status
    •  number of validation issues that tracking down
  • Identified issue using HL7 terminology validator (didn’t have IDC9 loaded)
  • Reported problem with it flagging unrecognized extensions
  • Do we need to have tests to see dataAbsentReason (DAR) used at least once? 
    • Considering At least the must supports
  • Discuss whether should limit MR profile: with intent = 'order'  to be computable.

Next steps:

  • Follow up for trackers to Hl7 to add "unknown" concept to the following Base FHIR resources.
    •  - AllergyIntolerance.clinicalStatus
    •   - Condition.clinicalStatus
    •   - DocumentReference.status
    •   - Immunization.status
    •   - Goal.lifecycleStatus
  • Technical Corrections to US Core
    • On CapabilityStatement Server page remove Provenance requirement from Medication, Location, Practitioner, PractitionerRole, and Organization 
    • In USCDI Table = change 'MedicationStatement' change to 'MedicationRequest'Remove MedicationStatement on guidance page.
    • Clarify that Location/PractitionerRole are not being referenced by other resources intentionally as part of a tracker item. 
    •  Fix bullet 2 in medication list guidance to clarify in intent = 'order'  (should be sub-bulleted)
    •  Add Write to DocRef QuickStart (removed from 3.1.0 in editing error)
    •  Add explicit SHALL support search with status if status required to the guidance on the For Servers Requiring Status
    •  Clarify text in clinical notes guidance on 'minimum required' to reference only the DocRef. and that the DiagnosticReport codes are strongly suggested but not required as id defined in the profile's bindings.
  • Discuss strategy and timing of a technical correction timeline  vis a vis the rule announcements. road map TBD
  • Strategy on expansion of US Core