Unattributed Code Systems

Copyright Fragment

This fragment is available on en/other.html

This publication includes IP covered under the following statements.

Copyright and Registered Trademark Uses

External References

Type Reference Content
web www.rfc-editor.org The NDH Server SHALL be protected using TLS in accordance with BCP 195 . The NDH Server SHOULD support OAuth 2.0 for authorization. The NDH Server SHOULD support FAST Security - Security for Scalable Registration, Authentication, and Authorization for dynamic client app discovery and authentication. The NDH Server SHOULD support SMART on FHIR for authorization of client requests to protected server resources. The NDH Server SHOULD support OpenID Connect for user authentication and identity management.
web www.rfc-editor.org The NDH Server SHALL be protected using TLS in accordance with BCP 195 . The NDH Server SHOULD support OAuth 2.0 for authorization. The NDH Server SHOULD support FAST Security - Security for Scalable Registration, Authentication, and Authorization for dynamic client app discovery and authentication. The NDH Server SHOULD support SMART on FHIR for authorization of client requests to protected server resources. The NDH Server SHOULD support OpenID Connect for user authentication and identity management.
web openid.net The NDH Server SHALL be protected using TLS in accordance with BCP 195 . The NDH Server SHOULD support OAuth 2.0 for authorization. The NDH Server SHOULD support FAST Security - Security for Scalable Registration, Authentication, and Authorization for dynamic client app discovery and authentication. The NDH Server SHOULD support SMART on FHIR for authorization of client requests to protected server resources. The NDH Server SHOULD support OpenID Connect for user authentication and identity management.
web example.org managingOrganization : http://example.org/fhir/Organization/AcmeHealth
web example.com contact : https://example.com/fhir/app-config.html
web acme-ehr-server.example.com address : https://acme-ehr-server.example.com/fhir
web example.org address : https://example.org/urlofportal-acmect
web example.org address : https://example.org/sqlonfhir-r4-azurewebsites/fhir
web www.hanssolo.com telecom : ph: (111)-222-3333, https://www.hanssolo.com
web www.hgh.com telecom : ph: (111)-222-3333, https://www.hgh.com
web www.orga.com telecom : ph: (111)-222-3333, https://www.orga.com
web www.orga.com telecom : ph: (777)-888-9999, https://www.orga.com
web www.orga.com telecom : ph: (444)-555-666, https://www.orga.com
web www.orga.com telecom : ph: (222)-333-4444, https://www.orga.com
web www.acmeofct.com telecom : ph: (111)-222-3333, https://www.acmeofct.com
web www.bixboxretailer.com telecom : ph: (111)-222-3333, https://www.bixboxretailer.com
web example.org telecom : ph: (123)-222-4444, https://example.org/blue-cross-blue-shield-ct-org
web www.burrclinic.com telecom : ph: (111)-222-3333, https://www.burrclinic.com
web www.medicare.example.com ratingSystem : https://www.medicare.example.com/care-compare/
web www.medicare.example.com ratingType : https://www.medicare.example.com/care-compare/resources/hospital/overall-star-rating/
web example.com ratingType : http://example.com/cms-care-compare/rating-component/safety
web example.com ratingType : http://example.com/cms-care-compare/rating-component/readmission
web example.com ratingType : http://example.com/cms-care-compare/rating-component/patient-experience
web www.examplehospital.com telecom : ph: (111)-222-3333, https://www.examplehospital.com
web www.hartfordgeneralhospital.com telecom : ph: (111)-222-3333, https://www.hartfordgeneralhospital.com
web www.org-manage-network.com telecom : ph: (123)-222-3333, https://www.org-manage-network.com
web www.org-one-with-network1-and-network2.com telecom : ph: (123)-333-3333, https://www.org-one-with-network1-and-network2.com
web www.pharmchain.com telecom : ph: (111)-222-3333, https://www.pharmchain.com
web www.PractitionerOneNetwork1Role.com telecom : https://www.PractitionerOneNetwork1Role.com
web www.PractitionerOneNetwork2Role.com telecom : https://www.PractitionerOneNetwork2Role.com
web www.PractitionerTwoNetwork1LeftAfterSixMonthRole.com telecom : https://www.PractitionerTwoNetwork1LeftAfterSixMonthRole.com
web example.org endpoint : https://example.org/Endpoints/d7dcc004-808d-452b-8030-3a3a13cd871d
web github.com National Directory of Healthcare Providers & Services (NDH) Implementation Guide, published by HL7 International / Patient Administration. This guide is not an authorized publication; it is the continuous build for version 2.0.0-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-us-ndh/ and changes regularly. See the Directory of published versions
web www.caqh.org Providers and service organizations often have to submit and manage information about themselves and their relationships to a variety of stakeholders. In the US healthcare sector, providers often contract with ten or more health plans, and are required to regularly submit similar information to each plan for inclusion in a given provider network and directory. Likewise, provider credentialing and hospital privileging processes require similar documentation. The Council for Affordable Quality Healthcare estimated that just maintaining provider databases costs the US healthcare industry at least $2 billion annually.
web www.iso.org ISO maintains the copyright on the country codes, and controls its use carefully. For further details see the ISO 3166 web page: https://www.iso.org/iso-3166-country-codes.html
Show Usage
web ucum.org The UCUM codes, UCUM table (regardless of format), and UCUM Specification are copyright 1999-2009, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved. https://ucum.org/trac/wiki/TermsOfUse
Show Usage
web example.org Example Content-Location: http://example.org/status-tracking/request-123 (note that this is not necessarily a FHIR endpoint, and is not a true FHIR resource)
web github.com          https://github.com/smart-on-fhir/fhir-bulk-data-docs/blob/master/export.md#response—complete-status
web profiles.ihe.net This example was adapted from section 5.1.8 in the IHE Topologies white paper.
web profiles.ihe.net This example was adapted from section 5.2.2 in the IHE Topologies white paper.

Internal Images

../assets/images/usa.svg
../assets/images/usa.svg
NDH Exchange.png
NDH Exchange.png
NDH-Ecosystem.png
NDH-Ecosystem.png
tree-filter.png
tree-filter.png