http://nucc.org/provider-taxonomy
http://www.ama-assn.org/go/cpt
http://www.cms.gov/Medicare/Coding/ICD10
https://nahdo.org/sopt
https://www.cdc.gov/nhsn/cdaportal/terminology/codesystem/hsloc.html
urn:ietf:bcp:47
This fragment is available on ImplementationGuide-hl7.fhir.us.core.html
This publication includes IP covered under the following statements.
| Type | Reference | Content |
|---|---|---|
| web | snomed.info | US Core Interpreter Needed Extension : SNOMED CT: 373066001 (Yes (qualifier value)) |
| web | example.org | url : http://example.org/fhir/Binary/A12345 |
| web | snomed.info | SNOMED CT: 248153007 (Male (finding)) |
| web | snomed.info | SNOMED CT: 248152002 (Female (finding)) |
| web | snomed.info | SNOMED CT: 373066001 (Yes (qualifier value)) |
| web | en.wikipedia.org | Part of health record where healthcare professionals record details to document a patient's clinical status or achievements during the course of a hospitalization or over the course of outpatient care ( Wikipedia ) |
| web | asapnet.org | Certifying systems [, those that are participating in the ONC Health IT certification program,] SHALL ... follow the Project US@ Technical Specification for Patient Addresses Final Version 1.0 as the standard style guide for Patient.address.line and Patient.address.city for new and updated records. |
| web | en.wikipedia.org | US Core Clients should follow the principle of least privilege and access only the necessary resources. |
| web | snomed.info | [When using SNOMED codes in US Core Profiles I]mplementers MAY use the default system URI [of SNOMED CT ], which refers to an unspecified edition/version [of SNOMED] |
| web | snomed.info | [To enable] terminology Servers to be able to validate US Edition-only codes [of SNOMED CT ], implementers SHOULD provide the accompanying system URI to describe the edition [see example 2 on US Core general guidance ] |
| web | unitsofmeasure.org | [If a] US Core Profiles binds the Quantity.code element in the Quantity datatype to the UCUM code system, [then] systems should also use UCUM for the optional valueRange and valueRatio datatypes (which are complex datatypes with Quantity elements) |
| web | unitsofmeasure.org | [If a] US Core Profiles binds the Quantity.code element in the Quantity datatype to the UCUM code system, [when] UCUM code [is] provided [it SHOULD be indicated in the Quantity.unit and Quantity.code elements with Quantity.system = "http://unitsofmeasure.org"] |
| web | unitsofmeasure.org | [If a] US Core Profiles binds the Quantity.code element in the Quantity datatype to the UCUM code system, [then] if UCUM units are unavailable, represent units in the unit element |
| web | www.nahdo.org | Implementers should refer to the PHDSC Payer Type Committee User’s Guide for the Source of Payment Typology when selecting codes. |
| web | wiki.ihe.net | [DocumentReference.type may also use] other category schemes such as the LOINC-based Document Class Value Set and IHE XDSclassCode |
| web | asapnet.org | Non-certifying systems[, systems that are not participating in the ONC Health IT certification program,] SHOULD follow the Project US@ Technical Specification for Patient Addresses Final Version 1.0 as the standard style guide for Patient.address.line and Patient.address.city for new and updated records. |
| web | asapnet.org | [For systems participating in the ONC Health IT certification program,] this requirement [to follow the Project US@ Technical Specification for Patient Addresses Final Version 1.0 for Patient.address.line and Patient.address.city] does not apply to historical records or documents that are exposed through FHIR-based APIs. [Organizations MAY choose not to use use Project US@ Technical Specification for Patient Addresses Final Version 1.0 when sending historical records] |
| web | www.iso.org | … this profile uses USPS Two Letter Alphabetic Codes for US states. When encoding addresses outside the US, systems SHOULD use the ISO 3166 subdivision codes . |
| web | www.nubc.org |
Category or kind of location after discharge
Binding: USEncounterDischargeDisposition ( preferred ) : National Uniform Billing Committee , manual UB-04, UB form locator 17 |
| web | snomed.info | 160245001 |
| web | snomed.info | 386053000 |
| web | snomed.info | 410606002 |
| web | github.com | US Core Implementation Guide, published by HL7 International / Cross-Group Projects. This guide is not an authorized publication; it is the continuous build for version 9.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/US-Core/ and changes regularly. See the Directory of published versions |
| web | example.org | http://example.org/fhir/Binary/1-note |
| web | example.org | http://example.org/fhir/Binary/procedure-note123.pdf |
| web | example.org | http://example.org/fhir/Binary/procedure-note456.pdf |
| web | example.org | http://example.org/fhir/Binary/discharge-summary789.pdf |
| web | about.usps.com |
"Material on this site is the copyrighted property of the United States Postal Service® (Postal Service™). All rights reserved. The information and images presented here may not under any circumstances be reproduced or used without prior written permission. Users may view and download material from this site only for the following purposes: (a) for personal, non-commercial home use; (b) where the materials clearly state that these materials may be copied and reproduced according to the terms stated in those particular pages; or (c) with the express written permission of the Postal Service. In all other cases, you will need written permission from the Postal Service to reproduce, republish, upload, post, transmit, distribute or publicly display material from this Web site. Users agree not to use the site for sale, trade or other commercial purposes. Users may not use language that is threatening, abusive, vulgar, discourteous or criminal. Users also may not post or transmit information or materials that would violate rights of any third party or which contains a virus or other harmful component. The Postal Service reserves the right to remove or edit any messages or material submitted by users."For more information, see
https://about.usps.com/who/legal/terms-of-use.htm
.
Show Usage
|
| web | about.usps.com | https://about.usps.com/who/legal/terms-of-use.htm |
| 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 | www.nubc.org |
Licensing information can be found here
These codes are listed within the UB-04 Data Specifications Manual. The Official UB-04 Data Specifications Manual, copyrighted by the American Hospital Association, is the only official source of UB-04 billing information adopted by the National Uniform Billing Committee. No other publication—governmental or private/commercial—can be considered authoritative. The AHA wants to make you aware that the use of codes, descriptions, or any other content contained in the manual to be used in a software application, publication, or any other derivative work must be properly licensed by the AHA. If your organization uses or intends to use any of the codes or other related content from the manual in this manner, please contact the AHA’s licensing manager, Tim Carlson, at 312.893.6816 or tcarlson@aha.org
Show Usage
|
| web | www.ihe.net |
Some content from IHE® Copyright © 2015 IHE International, Inc
.
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 | directtrust.org | This email address is associated with a "Direct Secure Messaging" service. This extension can only be used on contact points where the system = 'email' |
| web | directtrust.org | Simple Extension with the type boolean: This email address is associated with a "Direct Secure Messaging" service. This extension can only be used on contact points where the system = 'email' |
| web | wiki.ihe.net | In addition to the US Core DocumentReference Category value set, other category schemes such as the LOINC-based Document Class Value Set and IHE XDSclassCode may be used to facilitate the sharing of health documents. § |
| web | www.nubc.org | National Uniform Billing Committee , manual UB-04, UB form locator 17 |
| web | www.iso.org |
2
For Location.address.state
, this profile uses USPS Two Letter Alphabetic Codes for US states. When encoding addresses outside the US, systems SHOULD
use the ISO 3166 subdivision codes
.
§
|
| web | unitsofmeasure.org | The clinical test or procedure result value. If a numeric value, valueQuantity.code SHALL be selected from UCUM . A FHIR UCUM Codes value set that defines all UCUM codes is in the FHIR specification. |
| web | unitsofmeasure.org | if the result value is a numeric quantity, a standard UCUM unit |
| web | unitsofmeasure.org | The Laboratory result value. If a coded value, the valueCodeableConcept.code SHOULD be selected from SNOMED CT if the concept exists. If a numeric value, valueQuantity.code SHALL be selected from UCUM . A FHIR UCUM Codes value set that defines all UCUM codes is in the FHIR specification. |
| web | snomed.info | if the result value is a coded value , a standard SNOMED CT |
| web | unitsofmeasure.org | if the result value is a numeric quantity and coded quantity units are used, UCUM is required. |
| web | www.iso.org |
2
For Organization.address.state
, this profile uses USPS Two Letter Alphabetic Codes for US states. When encoding addresses outside the US, systems SHOULD
use the ISO 3166 subdivision codes
.
§
|
| web | asapnet.org | 1 For new and updated records, Certifying Systems SHALL and non-Certifying Systems SHOULD enable the users who enter patient addresses to follow the Project US@ Technical Specification for Patient Addresses Final Version 1.0 , which is required by the USCDI Patient Demographics Data Class §,§ |
| web | www.iso.org |
1
For Patient.address.state
, this profile uses USPS Two Letter Alphabetic Codes for US states. When encoding addresses outside the US, systems SHOULD
use the ISO 3166 subdivision codes
.
§
|
| web | www.iso.org |
3
For Practitioner.address.state
, this profile uses USPS Two Letter Alphabetic Codes for US states. When encoding addresses outside the US, systems SHOULD
use the ISO 3166 subdivision codes
.
§
|
| web | ihe.net | The US Core PractitionerRole Profile inherits from the FHIR PractitionerRole resource; refer to it for scope and usage definitions. This profile sets minimum expectations for the PractitionerRole Resource to record, search, and fetch the practitioner role information. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. The requirements for the US Core Practitioner were drawn from the Argonaut Provider Directory , IHE Healthcare Provider Directory and the ONC Provider Directory Workshop . |
| web | confluence.oncprojectracking.org | The US Core PractitionerRole Profile inherits from the FHIR PractitionerRole resource; refer to it for scope and usage definitions. This profile sets minimum expectations for the PractitionerRole Resource to record, search, and fetch the practitioner role information. It specifies which core elements, extensions, vocabularies, and value sets SHALL be present and constrains how the elements are used. Providing the floor for standards development for specific use cases promotes interoperability and adoption. The requirements for the US Core Practitioner were drawn from the Argonaut Provider Directory , IHE Healthcare Provider Directory and the ONC Provider Directory Workshop . |
| web | www.iso.org |
1
For RelatedPerson.address.state
, this profile uses USPS Two Letter Alphabetic Codes for US states. When encoding addresses outside the US, systems SHOULD
use the ISO 3166 subdivision codes
.
§
|
| web | browser.ihtsdotools.org | 108252007 Laboratory procedure (procedure) |
| web | browser.ihtsdotools.org | 363679005 Imaging (procedure) |
| web | browser.ihtsdotools.org |
386053000 Evaluation procedure (procedure)
, 410606002 Social service procedure (procedure) , or 387713003 Surgical procedure (procedure) |
| web | browser.ihtsdotools.org |
386053000 Evaluation procedure (procedure)
, 410606002 Social service procedure (procedure) , or 387713003 Surgical procedure (procedure) |
| web | browser.ihtsdotools.org |
386053000 Evaluation procedure (procedure)
, 410606002 Social service procedure (procedure) , or 387713003 Surgical procedure (procedure) |
| web | github.com | Resolved - change required :Confusing for commercial vendor. Reads very confusing. ( FHIR-30783 ) proposal is to make the differential tab the default view, see publishing plans here timeline unknown. |
| web | github.com | The following examples are published in this guide, and all are available as downloadable zip files here . Another source of examples that conform to this guide is the synthetic patient data generated by Synthea TM in the FHIR R4 format. |
| web | snomed.info | SNOMED CT (Systematized Nomenclature of Medicine – Clinical Terms) is a comprehensive clinical terminology widely used in healthcare to support the electronic exchange of clinical health information. US Core uses the US Edition of SNOMED CT, a standalone release that combines the content of the US Extension and the International releases of SNOMED CT. It is used extensively in US CORE for various clinical concepts, including problems, procedures, allergies, and laboratory results. When using SNOMED codes in US Core Profiles, implementers MAY use the default system URI, which refers to an unspecified edition/version, § as shown in option one below. However, for terminology Servers to be able to validate US Edition-only codes, implementers SHOULD provide the accompanying system URI to describe the edition as shown in option two. § |
| web | unitsofmeasure.org |
Some US Core Profiles bind the Quantity.code
element in the Quantity datatype to the UCUM
code system. For example, in the US Core Laboratory Result Observation Profile
, Observation.valueQuantity
, Observation.referenceRange.low
, and Observation.referenceRange.high
are bound to UCUM. Systems should also use UCUM for the optional valueRange
and valueRatio
datatypes (which are complex datatypes with Quantity elements).
§
A FHIR UCUM Codes ValueSet
that defines all UCUM codes is in the FHIR specification. This guidance specifies how to represent the Quantity datatype when the correct UCUM units are missing or when the units are missing, which will likely occur in the real world.
|
| web | fhir-open-api-dstu2.smarthealthit.org | base: The Service Root URL (e.g., " https://fhir-open-api-dstu2.smarthealthit.org ”) |
| web | httpwg.org |
The HTTP Cache-Control
response header stores a response associated with a request and reuses the stored response for subsequent requests. If a Cache-Control
header is present in the Server response headers, the Clients SHOULD NOT
search the same data within the time stated in the Cache-Control
header.
§
|
| web | asapnet.org | Certifying systems [, those that are participating in the ONC Health IT certification program,] SHALL … follow the Project US@ Technical Specification for Patient Addresses Final Version 1.0 as the standard style guide for Patient.address.line and Patient.address.city for new and updated records. |
| web | en.wikipedia.org | Each US Core Profile page includes a "Quick Start" section summarizing each profile's supported search transactions and scopes. Servers MAY support other scopes in addition to those listed below and in the Quick Start sections. § US Core Clients should follow the principle of least privilege and access only the necessary resources. § In other words, if a Client needs only vital sign observations, it should request access only to Observations with a category of "vital-signs". Note that a granular scope grants access to all resources matching that granular scope regardless of whether other categories are present. |
| web | www.nachc.org | Clinician administers a survey to gather information (for example, the Protocol for Responding to and Assessing Patients' Assets, Risks, and Experiences (PRAPARE) Survey ) |
| web | en.wikipedia.org | Screening and Assessments can be structured survey instruments consisting of questions with various responses, including true/false, coded, textual, and multiple choice. Examples include PRAPARE, Apgar score , and PHQ-9 . US Core defines two ways to represent the questions and responses to these screening and assessment instruments: |
| web | en.wikipedia.org | Screening and Assessments can be structured survey instruments consisting of questions with various responses, including true/false, coded, textual, and multiple choice. Examples include PRAPARE, Apgar score , and PHQ-9 . US Core defines two ways to represent the questions and responses to these screening and assessment instruments: |
| web | heart.org | The Physical Activity Observation Questions are panel item codes taken from the Physical Activity Implementation Guide , sponsored by the American Heart Association and the Physical Activity Alliance . In addition to contributing to the terminology for the USCDI Health Assessments Physical Activity Data Element, the guide documents a standardized way of measuring and sharing a patient's physical activity. |
| web | paamovewithus.org | The Physical Activity Observation Questions are panel item codes taken from the Physical Activity Implementation Guide , sponsored by the American Heart Association and the Physical Activity Alliance . In addition to contributing to the terminology for the USCDI Health Assessments Physical Activity Data Element, the guide documents a standardized way of measuring and sharing a patient's physical activity. |
| web | snomed.info | SNOMED |
| web | unitsofmeasure.org | UCUM |
| web | www.nubc.org | AHA NUBC Patient Discharge Status Codes |
| web | www.ada.org | Code on Dental Procedures and Nomenclature |
| web | www.ama-assn.org | Current Procedural Terminology (CPT®) |
| web | dicom.nema.org | DICOM Controlled Terminology |
| web | ihe.net | IHE Format Code set for use with Document Sharing |
| web | nucc.org | NUCC Provider Taxonomy |
| web | snomed.info | SNOMED CT (all versions) |
| web | www.usps.com | USPS State Codes |
| web | unitsofmeasure.org | Unified Code for Units of Measure (UCUM) |
|
ArgoR4Meds_1.svg
|
|
ArgoR4Meds_3.svg
|
|
ArgoR4Meds_4.svg
|
|
DiagnosticReport_DocumentReference_Resource_Overlap.png
|
|
Must_Support_AllergyIntolerance.png
|
|
Must_Support_AllergyIntolerance_clinicalStatus.png
|
|
Must_Support_AllergyIntolerance_code.png
|
|
Must_Support_DiagnosticReport_category.png
|
|
Must_Support_DiagnosticReport_issued.png
|
|
Must_Support_DiagnosticReport_presentedForm.png
|
|
Must_Support_Differential_View.png
|
|
Must_Support_DocumentReference.png
|
|
Must_Support_DocumentReference_category.png
|
|
Must_Support_Key_View.png
|
|
Must_Support_MedicationRequest.reported.png
|
|
Must_Support_Observation.effective.png
|
|
Must_Support_Observation.value.png
|
|
Must_Support_Organization_identifier.png
|
|
Must_Support_Patient_name.png
|
|
Must_Support_Patient_telecom.png
|
|
Must_Support_Snapshot_View.png
|
|
Must_Support_vital_signs.performer.png
|
|
Provenance_HIE_Redistribution.svg
|
|
Provenance_HIE_Transformation.svg
|
|
Provenance_Recon_Single_Organization.svg
|
|
Provenance_Recon_Workflow_Step2.svg
|
|
USCDI.png
|
|
US_Core_Growth_Path.jpg
|
|
allergies-and-intolerances.png
|
|
basic_fhir_restful_interaction.svg
|
|
both-url.jpg
|
|
care-plan.png
|
|
care-team-members.png
|
|
clinical-notes.png
|
|
clinical-tests.png
|
|
diagnostic-imaging.png
|
|
encounter.png
|
|
facility-information.png
|
|
family-health-history.png
|
|
fhir-write1.svg
|
|
fhir-write2.svg
|
|
goals-and-preferences.png
|
|
health-insurance-information.png
|
|
health-status-assessments.png
|
|
immunizations.png
|
|
laboratory.png
|
|
medical-devices.png
|
|
medications.png
|
|
modifier-element-view.png
|
|
orders.png
|
|
patient-demographics.png
|
|
problems.png
|
|
procedures.png
|
|
provenance.png
|
|
relationships.svg
|
|
screening_and_assessments.svg
|
|
sdoh_condition.svg
|
|
todo.png
|
|
tree-filter.png
|
|
uscore-observation-assessment-structure.svg
|
|
vital-signs.png
|
|
vsac-1.png
|
|
vsac-2.png
|
|
vsac-3.png
|
|
yearly-updates.png
|