1 / 9

HPD / HPDPLUS Comparison From a Direct Implementation point of view

HPD / HPDPLUS Comparison From a Direct Implementation point of view . HPD capabilities. HPD can store direct addresses for Individuals in a field call HPD_MEDICAL_RECORDS_ADDRESS Field can hold multiple addresses, but no metadata about affiliated practices or organizations.

marrim
Download Presentation

HPD / HPDPLUS Comparison From a Direct Implementation point of view

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. HPD / HPDPLUS Comparison From a Direct Implementation point of view

  2. HPD capabilities • HPD can store direct addresses for Individuals in a field call HPD_MEDICAL_RECORDS_ADDRESS • Field can hold multiple addresses, but no metadata about affiliated practices or organizations. • A list of provider organizations can be obtained from separate field but there is no correlation between orgs and addresses. • Multiple Certificates can also be stored, but not by address. Certs need to opened to fined affiliated direct address • Direct addresses for Organizations can be stored in a similar fashion

  3. HPDPlus enhanced capabilities • S&I recommended concept of Individual/Organization relationship with data • Each relationship can have multiple electronic services, for example Direct address • This allows a specific lookup of a providers Direct address by affiliated organization • Direct addresses for Organizations can be stored in a similar service based fashion. • Metadata about services can be stored. For Direct this includes payload types (CCD, C32, PDF, Text)

  4. HPD Basic Class Model

  5. HPDPlus Basic Class Model

  6. Complexity ComparisonClasses required

  7. What it means • In the standard referral use case, HPDPlus makes it much simpler to determine the correct address for provider who has multiple addresses. • Eliminates guess work • Payload capability is very important and can be easily determined in HPDPlus as well. • Still backwards compatible if HISP wants to allow for it.

  8. Where it’s going • This may all be moot. HPD was never fully “bought off” in IHE, still considered trial. • IHE is now entertaining HPDPlusmods within HPD. • C601 is being brought up in IHE and will probably be accepted. If that happens there will be on HPD again, with plus features.

  9. EHR/HIE Interop Work Group Use Cases • Provider search • This use case represents probably the primary functional use case. A user looks up a colleague based on name and retrieves the desired direct address • Search of provider by first and last name (substring) • Pick a provider, get list of organizations • Pick an Org; Get List of services detail for  one of these provider/organizations • Pick the Direct service and get the Direct Address • Organization Search • A variation is when a user knows a practice, and wants to get the direct address of a specific provider in that practice. • Get list of Organizations by org name (approx match) • Pick an Org; get a list of providers by provider name • Pick a provider; get List of service details • Pick the Direct service and get the Direct Address

More Related