Skip to content

PAS Encounter (Da Vinci PAS 2.1.0)

PAS Encounter is a Da Vinci PAS 2.1.0 profile on the FHIR R4 Encounter resource. It marks 22 elements as must-support; the rows below list each constrained element's cardinality and binding strength.

Profileprofile-encounter
Implementation GuideDa Vinci PAS 2.1.0
Base resourceEncounter
Canonical URLhttp://hl7.org/fhir/us/davinci-pas/StructureDefinition/profile-encounter
Must-support elements22
Constrained elements with bindings9
Encounter.meta0..1, must support
Encounter.meta.lastUpdated0..1, must support
Encounter.identifier0..*, must support
Encounter.identifier.system1..1, must support
Encounter.identifier.value1..1, must support
Encounter.status1..1, must support, binding: required
Encounter.statusHistory.status1..1, binding: required
Encounter.statusHistory.period1..1
Encounter.class1..1, must support, binding: extensible
Encounter.classHistory.class1..1, binding: extensible
Encounter.classHistory.period1..1
Encounter.type1..* (base 0..*), must support, binding: required
Encounter.subject1..1 (base 0..1), must support
Encounter.participant0..*, must support
Encounter.participant.type0..*, must support, binding: extensible
Encounter.participant.period0..1, must support
Encounter.participant.individual0..1, must support
Encounter.period0..1, must support
Encounter.reasonCode0..*, must support, binding: preferred
Encounter.reasonReference0..*, must support
Encounter.diagnosis.condition1..1
Encounter.hospitalization0..1, must support
Encounter.hospitalization.admitSource0..1, must support, binding: required
Encounter.hospitalization.dischargeDisposition0..1, must support, binding: preferred
Encounter.location0..*, must support
Encounter.location.location1..1, must support
Encounter.serviceProvider0..1, must support

Example

pidgeon data install fhir-davinci-pas-2.1
pidgeon conform --endpoint https://your-fhir-base/fhir --ig davinci-pas-2.1 --ci

The conform run walks the live endpoint and grades sampled resources against the installed Da Vinci PAS profiles. A failed report exits non-zero; --ci also fails the run on must-support gaps (MUSTSUPPORT-*) and stub-profile fallbacks (CONFORM_STUB_PROFILE).

Validation context

  • strict Profile validation grades an instance against this profile's snapshot: cardinality findings carry FHIR-PROFILE-CARDINALITY and terminology binding findings carry FHIR-PROFILE-BINDING.(FHIR-PROFILE-CARDINALITY)
  • strict Under pidgeon conform --ci, a sampled resource missing one of this profile's must-support elements fails the run with a MUSTSUPPORT-<element> rule id.
  • strict If the fhir-davinci-pas-2.1 package is not installed, validation falls back to an embedded subset stub and the report is flagged CONFORM_STUB_PROFILE; under --ci that warning fails the run.(CONFORM_STUB_PROFILE)

This answer, in your terminal

pidgeon conform --endpoint https://your-fhir-base/fhir --ig davinci-pas-2.1 --ci

Wire it into your AI agent:

claude mcp add pidgeon -- npx -y @pidgeonhealth/mcp

Download Post free to browse this reference with generation attached.

FHIR® R4 © Health Level Seven International. FHIR R4 specification content is used under its CC0 license; this page is a derivative work and is not endorsed by HL7 International.

HL7® and FHIR® are registered trademarks of Health Level Seven International.

Published by Pattern Engine LLC (Pidgeon Health).

Rendered from the same machine-readable definitions the Pidgeon engine validates against. Exported from the installed fhir-davinci-pas-2.1 package (2.1.0, CC0) through the Pidgeon engine's profile loader.