Stream: Da Vinci CRD
Topic: Place of Service for CRD
Nagesh Bashyam (Oct 09 2019 at 18:11):
Another Quick Question on CRD, our Clients is currently receiving CMS Place of Service codes (https://www.cms.gov/Medicare/Coding/place-of-service-codes/Place_of_Service_Code_Set.html) as part of EDI transactions to determine coverage requirements. We are planning to use the Location.type data element for Place of Service, however the binding currently is extensible but bound to (http://build.fhir.org/v3/ServiceDeliveryLocationRoleType/vs.html). Should we map the CMS Place of Codes with the LocationRoleType codes ? Or is there a different data element that should be used to send this detail ?
Lloyd McKenzie (Oct 09 2019 at 19:28):
I can't think of any other place where this would go. Most look mappable and the base FHIR spec currently mandates mapping. It might be worthwhile for us to create and publish a standard mapping. It's certainly possible to send the CMS codes too as a translation if additional nuance is needed and there isn't a 1..1 translation. @Paul Knapp @MaryKay McDaniel @Robert Dieterle?
Paul Knapp (Oct 09 2019 at 22:48):
@Nagesh Bashyam Claim.item.location.type in the coding.systema and .coding.code.
Nagesh Bashyam (Oct 10 2019 at 03:43):
@Paul Knapp , Since this is CRD, the transaction is referencing future orders and their place of service, the claim object is not yet created. So I will pass the Place of Service as part of the additional coding elements and also pick the appropriate one from the currently bound value set .
Last updated: Apr 12 2022 at 19:14 UTC
