Stream: Da Vinci
Topic: PDEX Plan Net
Matt Elrod (Sep 01 2020 at 15:29):
When comparing DaVinci PDEX Plan Net’s structure in Logical View and rendering we are seeing some differences. Please see below for one example.
In Resource Profile: PlannetPractitioner there are sub-elements (e.g. Practitioner.identifier.id, Practitioner.identifier.extension etc), in the “Practitioner.identifier:NPI” in Logical View.
image.png
In the following JSON structure definition, row 1560 to 1613 is the element of “Practitioner.identifier:NPI”. This element is followed by element “Practioner.active” whose data begin at row 1615. There is no sub elements definition (e.g. Practitioner.identifier.id, Practitioner.identifier.extension etc) between those 2 elements.
image.png
Any thoughts about this discrepancy.
James Derrickson (May 10 2021 at 18:31):
Noticing that the requirements for address Search for a Location is slightly different that an address search for an Organization. Why would these be different?
Da Vinci - Plan Net: from: http://hl7.org/fhir/us/davinci-pdex-plan-net/artifacts.html#2
Plannet_sp_location_address Select Locations with the specified address
Plannet_sp_organization_address Select organizations with the specified address (matches any of the string elements of an address)
R4 Defines:
http://hl7.org/fhir/R4/location.html#search
For Location Search - address string A (part of the) address of the location
For Organization Search -
http://hl7.org/fhir/R4/organization.html#search
address string A server defined search that may match any of the string fields in the Address, including line, city, district, state, country, postalCode, and/or text
Last updated: Apr 12 2022 at 19:14 UTC
