HPD USA National Extension Wiki Specification: Difference between revisions
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
#* The information found will be based on the HPD data model and required attributes in it. The query MUST support for querying of all required attributes as per this national extension. The query MUST allow for, and gracefully handle, queries for all optional attributes defined in this national extension, or base IHE HPD. | #* The information found will be based on the HPD data model and required attributes in it. The query MUST support for querying of all required attributes as per this national extension. The query MUST allow for, and gracefully handle, queries for all optional attributes defined in this national extension, or base IHE HPD. | ||
#* Attributes of particular focus include: contact information, address, Direct Project / secure email address, SOAP service endpoints, FHIR resources, language, specialty, and x.509 certificate. | #* Attributes of particular focus include: contact information, address, Direct Project / secure email address, SOAP service endpoints, FHIR resources, language, specialty, and x.509 certificate. | ||
#* Eric note: How is this different, if at all, from the next query? | |||
# Find a list of individual providers that match a demographic. | |||
#* The demographic will be based on the HPD data model and required attributes. Based on the above, that needs to be (at least) address, specialty, and language. | |||
# Find information on an organizational provider. | # Find information on an organizational provider. | ||
#* The information may largely be the same as an individual. | #* The information may largely be the same as an individual. | ||
# Find a list of organizational providers that match a demographic. Information may be largely the same as an individual. | # Find a list of organizational providers that match a demographic. Information may be largely the same as an individual. | ||
# Find all individual providers affiliated with an organization. | # Find all individual providers affiliated with an organization. | ||
Revision as of 11:37, 18 January 2016
HPD USA National Extension Wiki Specification
This page is what will soon become the USA National Extension specification proper. The broader context for this effort can be found in the wiki page Healthcare Provider Directory USA National Extension.
Required Queries
Implementers declaring conformance to the HPD USA National Extension MUST support the following queries.
- Find information on an individual provider.
- The information found will be based on the HPD data model and required attributes in it. The query MUST support for querying of all required attributes as per this national extension. The query MUST allow for, and gracefully handle, queries for all optional attributes defined in this national extension, or base IHE HPD.
- Attributes of particular focus include: contact information, address, Direct Project / secure email address, SOAP service endpoints, FHIR resources, language, specialty, and x.509 certificate.
- Eric note: How is this different, if at all, from the next query?
- Find a list of individual providers that match a demographic.
- The demographic will be based on the HPD data model and required attributes. Based on the above, that needs to be (at least) address, specialty, and language.
- Find information on an organizational provider.
- The information may largely be the same as an individual.
- Find a list of organizational providers that match a demographic. Information may be largely the same as an individual.
- Find all individual providers affiliated with an organization.
- I’ve heard people voice a need for this query, but I’m not sure I know the user story that goes with it. Is there one?
- Find electronic service information for an individual associated with an organization.
- This is supported, but it is not clear to me that it is outlined in the use cases above. We may want to be explicit about this use case: “Dr. Smith’s Direct address at Community Hospital rather than Dr. Smith’s Direct address at Smith Private Practice”.
- Find the organization, or organizations, associated with an individual or organization.
- Depending upon how we enable organizational service endpoints, it may be necessary to walk the hierarchy. For example, if I want the XCA query endpoint for Dr. Smith, I may need to look up the XCA query endpoint for the hospital Dr. Smith is affiliated with. If I want to look up the XCA query endpoint for an ED, I may need to look up the XCA endpoint at hospital housing the ED. Think of it as “given an individual, what is the parent organization?” and “given an organization, what is the parent organization?”.
Required LDAP/DSML Support
DSML Control Segment
Organizational Object Attribute Constraints
Human Provider Object Attribute Constraints
Organizational Object Extensions
Human Provider Object Extensions
Non-Normative Sample LDIF Schema File
Base IHE HPD International Change Proposals
Use Postal address object.