2019 Financial Track

Financial Management

Submitting WG/Project/Implementer Group

Financial Management Work Group

Justification

The FM resources for Claims and Reimbursement Resources are of interest internationally for implementing modern claim processing and connectathon exposure allows implementers to test and contribute to the resources as they evolve at DSTU. Since September 2013 FM resources have gained maturity and been tested in many of the connectathons with increased complexity of the test scenarios with each successive connectathon.

Proposed Track Lead

Coordinator: Paul Knapp {Knapp Consulting Inc.} Skype: paulknapp Benoit Schoeffler {Almerys}

Zulip: Connectathon Mgmt / Connectathon 20 - Financial Track

Expected participants

Knapp Consulting - Client and Server supporting all scenarios including the Veteran Institutional Claim to VA Payor Scenario

Almerys supporting most scenarios from the client and server perspectives

Payors/Providers/Support (Optum, Blue Cross/Blue Shield, others TBD)

CMS (BlueButton)

cognosante

Version of FHIR

The scenarios described below will be based on the FHIR R4 Published version.

Roles

FHIR Client - Eligibility Submitter

Enable the creation and submission of the Eligibility resource and the receiving or obtaining of an EligibilityResponse.

FHIR Server - Eligibility Processor

Support the receiving and processing of the Eligibility resource and creation of the EligibilityResponse resource.

FHIR Client - Claims Submitter

Enable the creation and submission of the Claim resource and the receiving or obtaining of a ClaimResponse. This may be as a Preauthorization, Predetermination or a completed Claim for actual adjudication.

FHIR Server - Claims Processor

Support the receiving and processing of the Claim resource as a: Preauthorization; Predetermination; or, actual Claim; and creation of the ClaimResponse resource.

FHIR Client - Claims Attachment Submitter

Enable the creation and submission of a Task containing a reference to the Communication resource and the receiving of a Task with the response. This may be as supporting information for a Preauthorization, Predetermination or a completed Claim for actual adjudication.

FHIR Server - Claims Attachment Processor

Support the receiving and processing of a Task referencing a Communication resource as supporting information for a Preauthorization, Predetermination or actual Claim; and creation of the Task resource containing the response.

FHIR Server - Claims Attachment Requestor

Support the receiving and processing of the Task resource and return a Task referencing a CommunicationRequest resource for a previously received and pended Preauthorization, Predetermination or actual Claim.

FHIR Client - Task: Polling, Status Check Submitter

Enable the creation and submission of the Task resource and the receiving or obtaining of a response Task or the requested resource. This may be to: request a Claim Reversal, request a deferred response, or a PaymentReconciliation or to obtain the processing status.

FHIR Server - Task: Polling, Status Check Processor

Support the receiving and processing of the Task resource and creation of the Task response resource or provision of the requested resource.

FHIR Server - PaymentReconciliation Processor

Support the receiving and processing of the Task (Poll) resource and creation of the PaymentReconciliation resource.

FHIR Server - Explanation of Benefit Processor

Support the receiving and processing of the Task (Poll) resource and creation of the ExplanationOfBenefit resource.

Scenarios

Each of the scenarios shown below may be implemented via FHIR REST or simple HTTP Request-Response exchange of Resources. The expected Track testing will be via a $submit operation where available, an HTTP POST Request-Response, with the resource, or exchangeable content, in the body of the HTTP content. While XML and JSON are both valid for rendering the FHIR resources, XML is preferred for the official testing to ensure as many participants as possible are able to find one or more Clients or Servers to test against. The testing scenarios shown below form the core of the "Financial" test track. There are eight test scenarios:

1. Submit an Eligibility, Retrieve/Receive an EligibilityResponse :via $submit operation
2. Submit a Pre-Authorization (Claim Resource) then an Attachment, Retrieve/Receive a ClaimResponse :via $submit operation
3. Submit a Claim, Retrieve/Receive a ClaimResponse :via REST (Create), Retrieve a ClaimResponse (Get) :via HTTP and Receive a ClaimResponse
4. Submit a Claim, Retrieve/Receive a ClaimResponse :via $submit operation
5. Retrieve deferred ClaimResponse via Task :via $submit operation
6. Retrieve the processing status via Task :via $submit operation
7. Retrieve a PaymentReconciliation via Task :via $submit operation
8. Retrieve an ExplanationOfBenefit via Task :via $submit operation

You may select one or more of these testing scenarios - whatever appeals to you most given your particular context. We encourage you to execute these scenarios with varying test data, but the only test executions which can be assured are those using resources based on the data provided here.

Submit an Eligibility, Retrieve/Receive an EligibilityResponse

Action: The FHIR Client will construct a Eligibility resource. To obtain the EligibilityResponse for the submitted resource via FHIR REST the client with perform a GET on EligibilityResponse with search parameters which may be expected to select the intended response.

Precondition: None

Success Criteria: Eligibility processed correctly by the Server (inspect via browser or available UI)

Bonus point: return plan details in addition to the indication of whether the coverage is in force.

Submit a Pre-Authorization (Claim Resource) then an Attachment, Retrieve/Receive a ClaimResponse

Action: The FHIR Client will construct a Claim resource indicating Pre-Authorization. The service will respond with a ClaimResponse indicating only receipt not adjudication of the Claim (Preauthorization). To obtain the adjudicated ClaimResponse the client must then submit an Attachment (Communication resource) containing any supporting material to which the Server will respond with a Task indicating success or failure with errors. Then the client may obtain the adjudicated ClaimResponse via the appropriate protocol. The ClaimResponse will contain an identifier which may be used during claim submission to indicate that the Preauthorization has been performed.

Precondition: None

Success Criteria: Preauthorization and Attachment processed correctly by the Server (inspect via browser or available UI)

Bonus point: For sending a business-appropriate form of attachment.

Submit a Claim via REST, Retrieve a ClaimResponse

Action: The FHIR Client will construct a Claim having either already submitted the supporting resources or with the supporting resources provided within the Claim as contained resources. To obtain the ClaimResponse for the submitted Claim the client will perform a GET on ClaimResponse with search parameters which may be expected to select the intended response.

Precondition: None

Success Criteria: Claim processed correctly by the Server (inspect via browser or available UI)

Bonus point: N/A

Submit a Claim via HTTP and Receive a ClaimResponse

Action: The FHIR Client will construct a Claim with the supporting information provided within the Claim as contained resources. The response to the Claim will be an OperationOutcome if the Claim cannot be understood or a ClaimResponse if it can.

If the priority=deferred then a ClaimResponse containing only errors or acknowledgement detail will be returned. The ClaimResponse containing adjudication details can be obtained later as the response to a Task (code=poll) resource, for example: [base]/ClaimResponse?request.identifier=http://happyvalley.com/claim%7C1500

Precondition: None

Success Criteria: Claim processed correctly by the Server (inspect via browser or available UI)

Bonus point: N/A

Submit a Claim via $submit and Receive a ClaimResponse

Action: The FHIR Client will construct a Claim with the supporting information provided within the Claim as contained resources. The response to the Claim will be an OperationOutcome if the Claim cannot be understood or a ClaimResponse if it can.

If the priority=deferred then a ClaimResponse containing only errors or acknowledgement detail will be returned. The ClaimResponse containing adjudication details can be obtained later as the response to a Task (code=poll) resource, for example: request.identifier=http://happyvalley.com/claim%7C1500

Precondition: None

Success Criteria: Claim processed correctly by the Server (inspect via browser or available UI)

Bonus point: N/A

Retrieve deferred ClaimResponse via Task

Action: Submission of a Task (code=poll) resource which contains a reference to the previously submitted claim will result in the creation, and perhaps return, of the ClaimResponse containing the adjudicated results of the previously submitted Claim.

Precondition: None

Success Criteria: ClaimResponse returned correctly by the Server and parsed and displayed in context by the Client

Bonus point: N/A

Retrieve the processing status (Task) via Task

Action: Submission of a Task (code=status) resource which contains a reference to the previously submitted claim will result in the creation and perhaps return of the Task containing the processing status of the previously submitted Claim.

Precondition: None

Success Criteria: Task returned correctly by the Server (inspect via browser or available UI)

Bonus point: N/A

Retrieve a PaymentReconciliation via Task

Action: Submission of a Task (code=poll) resource which contains a reference to the PaymentReconciliation class of Resources will result in the creation and possible return of the PaymentReconciliation containing the payments for the previously submitted Claims.

Precondition: None

Success Criteria: PaymentReconciliation returned correctly by the Server (inspect via browser or available UI)

Bonus point: N/A

Retrieve an ExplanationOfBenefit via Task

Action: Submission of a Task (code=poll) resource which contains a reference to the ExplanationOfBenefit class of Resources and a period and Coverage will result in the creation and possible return of the ExplanationOfBenefit.

Precondition: None

Success Criteria: ExplanationOfBenefit returned correctly by the Server (inspect via browser or available UI)

Bonus point: N/A

Sample Data

Claims

Field	Patient #1 Claim	Patient #2 Claim
Claim Number	1500	1501
Processing Priority	Normal	Normal
Claim Type	Oral Health	Oral Health
Name	John M. Smith (Usual)	Judy F. Robinson (Usual)
Gender	M	F
Birthdate	1973-04-14	1993-06-24
Exceptions		Full-time student (Code 1) at Rozdale University
Address	1234 Any Street Menlo Park, California 90123	1 Landingpad Lane Loma Linda, California 90310
Dentist	Dr. Darryl Dentist (# 904563) Happy Valley Clinic (# 1535)	Dr. Phil Amolar (# 678543) Happy Valley Clinic (# 1535)
Referral	Practitioner (# 720415) Reason: Rampant decay (Code 7)
Insurance	The Benefit Company (BINN# 654123) Certificate: A7G345, Plan (Policy): 123YHT56 SubPlan: 35 Dependent: 01 Relationship: Self Policy: Dental annual Individual Maximum of $2500, Basic Services at 80%, Major at 50%, no Orthodontic coverage	Health Management Corp (BINN# 564378) Certificate: RF98765 Plan (Policy): GALACTIC Dependent: 04 Relationship: Child Frank Robinson born 1953-05-14 Policy: Dental annual Individual Maximum of $2500, Basic Services at 100%, Major at 80%, lifetime individual Orthodontic coverage $6000 Vision: $200 per year, Pharmacy: 20% co-pay, $3500 individual annual maximum.
Service Code, Fee, Tooth Surface, Lab#1 Code, Lab#1 Fee, Lab#2 Code, Lab#2 Fee
Service #1	1102, $65.00	1101, $55.00
Service #2	21211, $105.00, 21, L	2102, $730.00
Service #3	27211, $900.00, 22, , 99111, $250.00	21211, $105, 21, L
Service #4		21212, $200.00, 42, DI
Service #5		11101, $135.00

Services

Code	Description	Fee
1101	Exam, comp, primary	55.00
1102	Exam, comp, mixed	60.00
1103	Exam, comp, permanent	65.00
1201	Exam, comp, primary	45.00
1205	Exam, emergency	75.00
2101	Radiograph, series (12)	530.00
2102	Radiograph, series (16)	730.00
2141	Radiograph, bytewing	530.00
2601	Radiograph, panoramic	420.00
11101	Polishing, 1 unit	35.00
11102	Polishing, 2 unit	70.00
11103	Polishing, 3 unit	105.00
11104	Polishing, 4 unit	135.00
21211	Amalgam, 1 surface	105.00
21212	Amalgam, 2 surface	200.00
27211	Crown, PFM	900.00
99111	Lab, commercial	250.00
99333	Lab, in office	200.00
99555	Lab, Expense	0.00