This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "201609 Attachments"

From HL7Wiki
Jump to navigation Jump to search
Line 35: Line 35:
 
==Scenarios==
 
==Scenarios==
 
<!-- What will be the actions performed by participants? -->
 
<!-- What will be the actions performed by participants? -->
 +
For all scenarios below, the following types of attachments are allowed:
 +
* PDF attachment
 +
* Unstructured C-CDA attachment
 +
* Structured C-CDA attachment
 +
* C-CDA on FHIR attachment
  
 
===Prior Authorization===
 
===Prior Authorization===
:Action: <!--Who does what?  (Use the role names listed above when referring to the participants -->
+
:Action: Provider creates an attachment and sends it to the payer.
:Precondition: <!-- What setup is required prior to executing this step? -->
+
:Precondition: Prior authorization has occurred, and the provider has an id (i.e. electronic staple) to associate the attachment with the claim.
:Success Criteria: <!-- How will the participants know if the test was successful? -->
+
:Success Criteria: Payer receives the attachment and is able to view it.
 
:Bonus point: <!-- Any additional complexity to make the scenario more challenging -->
 
:Bonus point: <!-- Any additional complexity to make the scenario more challenging -->
  

Revision as of 16:55, 17 June 2016


Attachments

Submitting WG/Project/Implementer Group

Attachments Work Group (AWG)

Justification

Proposed Track Lead

See Connectathon_Track_Lead_Responsibilities

  • Rick Geimer
    • Co-leads, Paul Knapp, Durwin Day

Expected participants

  • BCBS
  • HCSC
  • BCBSAL
  • Anthem
  • Optum

Roles

Please include information here regarding how much advance preparation will be required if creating a client and/or server.

Payer

Provider

Scenarios

For all scenarios below, the following types of attachments are allowed:

  • PDF attachment
  • Unstructured C-CDA attachment
  • Structured C-CDA attachment
  • C-CDA on FHIR attachment

Prior Authorization

Action: Provider creates an attachment and sends it to the payer.
Precondition: Prior authorization has occurred, and the provider has an id (i.e. electronic staple) to associate the attachment with the claim.
Success Criteria: Payer receives the attachment and is able to view it.
Bonus point:


Solicited

Action:
Precondition:
Success Criteria:
Bonus point:


Unsolicited

Action:
Precondition:
Success Criteria:
Bonus point:


TestScript(s)