This page is part of the FHIR Specification (v3.3.0: R4 Ballot 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
Financial Management Work Group | Maturity Level: N/A | Ballot Status: Informative | Compartments: Practitioner |
ProcessResponse with Pended status and request for additional information (id = "SR2499")
<ProcessResponse xmlns="http://hl7.org/fhir"> <id value="SR2499"/> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml">A ProcessResponse indicating pended status with a request for additional information.</div> </text> <contained> <CommunicationRequest> <id value="comreq-1"/> <identifier> <system value="http://www.jurisdiction.com/insurer/123456"/> <value value="ABC123"/> <!-- this is the value to which the response will refer --> </identifier> <status value="active"/> <category> <coding> <system value="http://acme.org/messagetypes"/> <code value="SolicitedAttachmentRequest"/> </coding> </category> <recipient> <identifier> <system value="http://www.jurisdiction.com/provideroffices"/> <value value="3456"/> </identifier> </recipient> <payload> <contentString value="Please provide the accident report and any associated pictures to support your Claim# DEF5647."/> </payload> <authoredOn value="2016-06-10T11:01:10-08:00"/> <sender> <identifier> <system value="http://www.jurisdiction.com/insurer"/> <value value="123456"/> </identifier> </sender> </CommunicationRequest> </contained> <identifier> <system value="http://www.BenefitsInc.com/fhir/processresponse"/> <value value="881222"/> </identifier> <status value="active"/> <created value="2014-08-16"/> <organization> <reference value="Organization/2"/> </organization> <request> <reference value="http://happyvalley.com/fhir/claim/12345"/> </request> <outcome value="pended"/> <disposition value="Additional information required."/> <requestProvider> <reference value="Organization/1"/> </requestProvider> <communicationRequest> <reference value="#comreq-1"/> </communicationRequest> </ProcessResponse>
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.