This page is part of the DaVinci Postable Remittance FHIR Implementation Guide (v1.0.0-ballot: STU 1 Ballot 1) based on FHIR (HL7® FHIR® Standard) R4. . For a full list of available versions, see the Directory of published versions

Conformance

Systems

This mplementation guide defines the responsibilities of the two types of systems:

Client systems are typically Electronic Medical Record (EHR) systems but could theoretically be any system needing to retrieve a postable remittance.

Server systems (or servers) are typically payer systems or clearing houses that act on behalf of payer organizations.

MustSupport

This implementation guide uses specific terminology to flag statements that have relevance for the evaluation of conformance with the guide:

• SHALL indicates requirements that must be met to be conformant with the specification.

• SHOULD indicates behaviors that ought to be adhered to to avoid suboptimal interoperability but which do not, for this version of the specification, affect the determination of specification conformance.

• MAY describes optional behaviors that are free to consider but where there is no recommendation for or against adoption.

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. Also see the mustSupport rules for the HRex which apply to content adhering to data elements profiled in those guides.