Some element have non-deterministic xpath expressions which make it difficult for CRUD operations. An indexing attribute should be provided. examples include:
provider/demographic/name
provider/demographic/name/commonName
provider/demographic/name/otherNames
facility/otherName
facility/operatingHours
provider/facilities/facility/service/operatingHours
In some cases, there is an attribute/set of attributes existing on the element that can be potentially used, but the attribute/set of attributes may not be required to have a unique value relative to its parent element. Examples include:
provider/organizations/organization (using @oid)
provider/facilities/facility (using @oid)
provider/facilities/facility/service (using @oid)
provider/credential (using the triple(@code,@codingSchema,number))
provider/codedType (using the pair(@code,@codingSchema))
provider/specialty (using the pair(@code,@codingSchema))
provider/demographic/address (using @type)
facility/address (using @type)
facility/codedType (using the pair(@code,@codingSchema))
facility/organizations (using @oid)
provider/facilities/facility/service/operatingHours (using @oid)
provider/facilities/facility/service/language (using the pair(@code,@codingSchema))
facility/language (using the pair(@code,@codingSchema))
Others are unclear if they should allow multiple or not. If not, they need some indexing attribute. For example:
provider/demographic/contactPoint (on the pair(@code,@codingSchema))
facility/contactPoint (on the pair(@code,@codingSchema))
Some element have non-deterministic xpath expressions which make it difficult for CRUD operations. An indexing attribute should be provided. examples include:
provider/demographic/name
provider/demographic/name/commonName
provider/demographic/name/otherNames
facility/otherName
facility/operatingHours
provider/facilities/facility/service/operatingHours
In some cases, there is an attribute/set of attributes existing on the element that can be potentially used, but the attribute/set of attributes may not be required to have a unique value relative to its parent element. Examples include:
provider/organizations/organization (using @oid)
provider/facilities/facility (using @oid)
provider/facilities/facility/service (using @oid)
provider/credential (using the triple(@code,@codingSchema,number))
provider/codedType (using the pair(@code,@codingSchema))
provider/specialty (using the pair(@code,@codingSchema))
provider/demographic/address (using @type)
facility/address (using @type)
facility/codedType (using the pair(@code,@codingSchema))
facility/organizations (using @oid)
provider/facilities/facility/service/operatingHours (using @oid)
provider/facilities/facility/service/language (using the pair(@code,@codingSchema))
facility/language (using the pair(@code,@codingSchema))
Others are unclear if they should allow multiple or not. If not, they need some indexing attribute. For example:
provider/demographic/contactPoint (on the pair(@code,@codingSchema))
facility/contactPoint (on the pair(@code,@codingSchema))