Stream: Da Vinci CRD
Topic: CRD Response Question
Nagesh Bashyam (Sep 17 2019 at 14:50):
Hello
As we are implementing the CRD use case with payers and providers, we are finding that some of the payers would like to send a CoverageEligibiltyResponse object along with response. An example here is shown below. The client would receive and store it somewhere for auditing and other purposes as needed.
Are there any issues with this response ? Please let us know.
{
"cards": [
{
"summary": "Authorization not required for Codeine prescription",
"indicator": "info",
"source":
{
"label": "Authorization not required for Codeine prescription",
"url": "http://Example/bundle/23435-43234-32432"
}
}
]
}
Isaac Vetter (Sep 17 2019 at 15:01):
Hey Nagesh, the intent of the card's source attribute is to optionally provide a human-readable web url that the user can access in a browser from the card to better understand the justification of the guidance. Other cds services have used this field to link to an academic journal article, or a CDC defined set of recommendations, etc.
Isaac Vetter (Sep 17 2019 at 15:03):
I understand that "some of the payers would like to send a CoverageEligibiltyResponse object along with response", but am less clear on:
1) if providers are able to receive or use this link and
2) how this source link improves the user's experience
Nagesh Bashyam (Sep 17 2019 at 16:05):
Good question, the current explanation i have heard is only for auditing purpose (it contains all the information that was sent) and received along with the authorization decision that was made.
Last updated: Apr 12 2022 at 19:14 UTC
