Artifacts: Need additional artifacts for the Pediatric Demog Option?

[lynnfel]

Section Number https://profiles.ihe.net/ITI/PDQm/artifacts.html#structures-resource-profiles

Issue When the Pediatric Demographics Option is supported, both the Consumer and Supplier have additional requirements. Do we need additional artifacts for this? StructureDefinition? CapabilityStatement?

Proposed Change When a Supplier Actor supports the Pediatric Demographic Option, these attributes become "Must Support":

• mother's maiden name
• patient.telecom --> It seems like we need to constrain this http://hl7.org/fhir/R4/datatypes.html#ContactPoint since the Supplier is required to be able to return Patient Home Telephone
• Patient.multipleBirth http://hl7.org/fhir/R4/patient-definitions.html#Patient.multipleBirth_x_ --> Interestingly, this can either be a boolean datatype or an integer datatype. Vol 1 https://profiles.ihe.net/ITI/PDQm/actor_options.html#13821-pediatric-demographics-option-- specifies that the Supplier shall be able to return Patient Multiple Birth Indicator and Patient Birth Order, but cardinality of this attribute is 0..1.

When a Consumer Actor supports the Pediatric Demographic Option, it shall be able to query by Mother's Maiden Name.

Priority:

• Medium: Significant issue or clarification. Requires discussion, but should not lead to long debate.

[JohnMoehrke]

Not clear to me how to handle this. Adding another structureDefinition simply to mark some elements MS, without any way to request that profile be used seems not helpful. There is already an expectation that any query parameter can be used, at the whim of the client; and all query parameters must be supported by servers; and all data elements the server has will be returned. The distinction of pediatric demographics option does not seem useful in the modern PDQm supplement, as it is part of the normal support. Can we eliminate this option? What benefit is it bringing?

[lynnfel]

I have never been a fan of this option, even in our HL7v2/v3 profiles. I would not object to removing it from PDQm.

However, we should get input from people who have deployed products with this functionality. Maybe there is value for them. My annoyance is largely because it was not documented well (historical source of CPs) and is a pain to test. That should not be why we drop it from this profile

[JohnMoehrke]

will remove pediatric option