This wiki has undergone a migration to Confluence found Here
Difference between revisions of "201601 Financial Management"
Jump to navigation
Jump to search
(Created page with "{{subst::Template for FHIR Connectathon Track Proposals}}") |
(Initial content added) |
||
| Line 2: | Line 2: | ||
[[Category:201601_FHIR_Connectathon_Track_Proposals|Jan 2016 Proposals]] | [[Category:201601_FHIR_Connectathon_Track_Proposals|Jan 2016 Proposals]] | ||
__NOTOC__ | __NOTOC__ | ||
| − | = | + | =Financial Management= |
==Submitting WG/Project/Implementer Group== | ==Submitting WG/Project/Implementer Group== | ||
| Line 12: | Line 12: | ||
==Proposed Track Lead== | ==Proposed Track Lead== | ||
<!-- Name, email and Skype id of individual who will coordinate the track at the connectathon --> | <!-- Name, email and Skype id of individual who will coordinate the track at the connectathon --> | ||
| + | Coordinator: [mailto:pknapp@pknapp.com Paul Knapp] | ||
==Expected participants== | ==Expected participants== | ||
| Line 18: | Line 19: | ||
==Roles== | ==Roles== | ||
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on --> | <!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on --> | ||
| − | === | + | ===FHIR Client - Claims Submitter=== |
<!-- Provide a description of the capabilities this role will have within the connectathon --> | <!-- Provide a description of the capabilities this role will have within the connectathon --> | ||
| + | Enable the creation and submission of the Claim resource. | ||
| + | |||
| + | ===FHIR Server - Claims Processor=== | ||
| + | <!-- Provide a description of the capabilities this role will have within the connectathon --> | ||
| + | Support the receiving and processing of the Claim resource and creation of the ClaimResponse resource. | ||
==Scenarios== | ==Scenarios== | ||
<!-- What will be the actions performed by participants? --> | <!-- What will be the actions performed by participants? --> | ||
| + | The testing scenarios shown below form the core of the "Financial" test track. There are three test scenarios: | ||
| + | #Submit a Claim via REST (Create), Retrieve a ClaimResponse (Get) | ||
| + | #Submit a Claim via WSI Web Services and Receive a ClaimResponse | ||
| + | #Retrieve deferred ClaimResponse via ProcessRequest | ||
| + | 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 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 with 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 FHIR Server (inspect via browser or available UI) | ||
| + | :Bonus point: N/A | ||
| + | |||
| + | ===Submit a Claim via WSI Web Services 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 ProcessRequest (action=poll) resource, for example: [base]/ClaimResponse?request.identifier=http://happyvalley.com/claim|1500 | ||
| + | :Precondition: None | ||
| + | :Success Criteria: Claim processed correctly by the FHIR Server (inspect via browser or available UI) | ||
| + | :Bonus point: N/A | ||
| − | === | + | ===Retrieve deferred ClaimResponse via ProcessRequest=== |
| − | :Action: | + | :Action: Submission of a ProcessRequest (action=poll) resource which contains a reference to the previously submitted claim via WSI Web Services will result in the return of the ClaimResponse containing the adjudicated results of the previously submitted Claim. |
| − | :Precondition: | + | :Precondition: None |
| − | :Success Criteria: | + | :Success Criteria: ClaimResponse returned correctly by the FHIR Server (inspect via browser or available UI) |
| − | :Bonus point: | + | :Bonus point: N/A |
<!-- Provide a description of each task --> | <!-- Provide a description of each task --> | ||
Revision as of 18:42, 18 November 2015
Financial Management
Submitting WG/Project/Implementer Group
Justification
Proposed Track Lead
Coordinator: Paul Knapp
Expected participants
Roles
FHIR Client - Claims Submitter
Enable the creation and submission of the Claim resource.
FHIR Server - Claims Processor
Support the receiving and processing of the Claim resource and creation of the ClaimResponse resource.
Scenarios
The testing scenarios shown below form the core of the "Financial" test track. There are three test scenarios:
- Submit a Claim via REST (Create), Retrieve a ClaimResponse (Get)
- Submit a Claim via WSI Web Services and Receive a ClaimResponse
- Retrieve deferred ClaimResponse via ProcessRequest
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 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 with 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 FHIR Server (inspect via browser or available UI)
- Bonus point: N/A
Submit a Claim via WSI Web Services 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 ProcessRequest (action=poll) resource, for example: [base]/ClaimResponse?request.identifier=http://happyvalley.com/claim%7C1500
- Precondition: None
- Success Criteria: Claim processed correctly by the FHIR Server (inspect via browser or available UI)
- Bonus point: N/A
Retrieve deferred ClaimResponse via ProcessRequest
- Action: Submission of a ProcessRequest (action=poll) resource which contains a reference to the previously submitted claim via WSI Web Services will result in the return of the ClaimResponse containing the adjudicated results of the previously submitted Claim.
- Precondition: None
- Success Criteria: ClaimResponse returned correctly by the FHIR Server (inspect via browser or available UI)
- Bonus point: N/A
