Domains
Direct Domain
A Direct domain is the URL at which a Direct email server is listening for Direct email traffic and from which it sends Direct email traffic.
A Direct domain is incompatible with a regular email address domain. For example, MyEHR.com cannot process both Direct and non-Direct email traffic - only one or the other.
Direct domains can be acquired, managed and configured by our partner or by Updox. We do not currently charge for this service.
Industry best practices strongly urge all Direct participants to configure a TLD with the word "direct" in it. For example: MyEHRDirect.com, DirectMyEHR.com, etc.
Updox strongly recommends not having "direct" as a subdomain of a TLD (direct.MyEHR.com, for example) in order to comply with industry best practices - it can lead to unwieldy Direct addresses (dr.thomas.finney@familypractice.direct.myehr.com, for example).
Once a partner has specified their "base" Direct domain, the full Direct domain for all practices created will use sub-domains of the vendor-level base Direct domain. If a partner's vendor-level base Direct domain is MyEHRDirect.com then their practices' Direct domains might be SomePracticeName.MyEhrDirect.com. To configure a practice's Direct domain, you may supply either the sub-domain only (SomePracticeName) or the full Direct domain (SomePracticeName.MyEhrDirect.com). A practice may NOT have a Direct domain that does not end with the vendor-level TLD. Therefore, for a vendor-level base Direct domain of MyEhrDirect.com, SomePracticeName.MyEhrDirect.com is valid, but SomePracticeName.MyPractice.com is not.
A practice's Direct domain can be the same as or different from their accountId. The two identifiers are maintained separately.
A practice's Direct domain can be set in the PracticeCreate/PracticeSave/PracticeUpdate API calls. It must be unique across the vendor.
Portal Domain
A Portal domain is the URL at which a patient may login to a given practice's Patient Portal in order to send/receive messages to the practice and to transmit CCD information to Providers.
Provisioning a custom Portal domain requires a two week lead time before availability.
Portal domains can be acquired, managed, and configured by our partner or by Updox. We do not currently charge for this service.
Only one custom Portal TLD per partner is supported. This means that Updox can supply a Patient Portal at MyEHRPortal.com. For a certain practice, patients could then access it by browsing to SomePracticeName.MyEHRPortal.com. A different practice might have their Patient portal at FamilyChiro.MyEHRPortal.com but Updox doesn't support having it at MyPortal.MyPractice.com, for example.
A practice's Portal domain can be the same as or different from their Direct domain. The two identifiers are maintained separately. This is not recommended, however, as having the word "direct" in a Portal domain link might be slightly confusing to patients.
A practice's Portal domain can be the same as or different from their accountId. The two identifiers are maintained separately.
A practice's Portal domain can be set in the PracticeCreate/PracticeSave/PracticeUpdate API calls. It must be unique across the vendor.
