This page is part of the DaVinci PDEX Plan Net (v1.2.0: STU 1) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

Confexpectations

This implementation guide uses specific terminology such as SHALL, SHOULD, MAY to flag statements that have relevance for the evaluation of conformance with the guide. As well, profiles in this implementation guide make use of the mustSupport element. Base expectations for the intepretations of these terms are set in the FHIR core specification and general Da Vinci-wide expectations are defined in HRex

Additional conformance expectations specific to this guide are as follows:

Conformance Expectations

• This guide inherits all conformance expectations identified in the Health Record Exchange (Hrex) Conformance Expectations section. All systems claiming conformance to this guide SHALL conform to the requirements listed in that section.

• Server systems claiming conformance to this guide SHALL meet the capability statement expectation requirements identified in the Plan-Net CapabilityStatement and SHALL have a CapabilityStatement that has a CapabilityStatement.instantiates with a URL of http://hl7.org/fhir/us/davinci-drug-formulary/CapabilityStatement/usdf-server or a URL to the appropriate version of the CapabilityStatement.

MustSupport

• The must support requirements for this IG inherit from the Conformance Expectations section of the Da Vinci HRex IG and from US Core.

When querying and reading the Plan-Net Profiles defined in this IG, Must Support on any profile data element SHALL be interpreted as follows:

Health Plan API Requirements

• Health Plan API actors SHALL be capable of populating all Must Support data elements as part of the query results.
• In situations where information on a particular Must Support data element is not present and the minimum cardinality is 0 , the Health Plan API actors SHALL NOT include the data elements in the resource instance returned as part of the query results.
• In situations where information on a particular data element is not present and the minimum cardinality is >0 SHALL send the reason for the missing information using values (such as nullFlavors) from the value set where they exist or use the dataAbsentReason extension.

Application Requirements

• Application actors SHALL be capable of processing resource instances containing the Must Support data elements without generating an error or causing the application to fail.
• Application actors SHOULD be capable of displaying the data elements for human use or storing the information for other purposes.
• When querying Health Plan API actors, Application actors SHALL interpret missing Must Support data elements within resource instances as data not present in the Health Plan API actors system.
• Consumer App actors SHALL be able to process resource instances containing Must Support data elements asserting missing information.