http://ihe.net/fhir/ihe.formatcode.fhir/CodeSystem/formatcode
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
https://www.usps.com/
urn:ietf:bcp:47
urn:iso:std:iso:11073:10101
urn:oid:2.16.840.1.113883.6.238
| Type | Reference | Content |
|---|---|---|
| web | snomed.info | US Core Interpreter Needed Extension : SNOMED CT 373066001 : Yes (qualifier value) |
| web | example.org | url : http://example.org/Binary/A12345 |
| web | snomed.info | SNOMED CT 373066001 : Yes (qualifier value) (version = http://snomed.info/sct/731000124108 ) |
| 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 | 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 8.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 | 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 | snomed.info | providing a more specific code, for example, the more specific LOINC, "81364-2 (Religious or cultural beliefs [Reported])" , a SNOMED CT concept, or a system-specific code |
| web | www.cda-adc.ca | Mappings for Canadian Dental Association eclaims standard ( http://www.cda-adc.ca/en/services/cdanet/ ) |
| web | www.pharmacists.ca | Mappings for Canadian Pharmacy Associaiton eclaims standard ( http://www.pharmacists.ca/ ) |
| web | www.nahdo.org |
The hierarchical nature of the Coverage.type
code system "Payer" (also known as the US Public Health Data Consortium Source of Payment Codes) may be unclear in the expansion, and some codes may be inappropriate for the use case. Implementers should refer to the PHDSC Payer Type Committee User's Guide
for the Source of Payment Typology when selecting codes.
|
| web | www.nahdo.org | The US Core team requested a stand-alone code for Medicare Part A from NAHDO . If this request is not approved, systems SHOULD use the X12 concept for Medicare Part A as a code translation to the SOP code "121" (see Using multiple codes with CodeableConcept Datatype ). |
| 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 of 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.nubc.org |
Category or kind of location after discharge Binding: USEncounterDischargeDisposition ( preferred ): National Uniform Billing Committee , manual UB-04, UB form locator 17 ele-1: All FHIR elements must have a @value or children |
| 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 | asapnet.org |
*
Systems SHOULD
follow the Project US@ Technical Specification for Patient Addresses Final Version 1.0
as the standard style guide for Location.address.line
and Location.address.city
.
|
| 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 | snomed.info | providing a more specific code, a SNOMED CT concept, or a system-specific code |
| 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 quantity, a standard SNOMED CT |
| web | snomed.info | providing a more specific code such as 'chemistry', a SNOMED CT concept, or a system-specific code |
| web | unitsofmeasure.org | if the result value is a numeric quantity and coded quantity units are used, UCUM is required. |
| web | www.omg.org | Mappings for ServD ( http://www.omg.org/spec/ServD/1.0/ ) |
| web | asapnet.org |
*
Systems SHOULD
follow the Project US@ Technical Specification for Patient Addresses Final Version 1.0
as the standard style guide for Organization.address.line
and Organization.address.city
.
|
| web | asapnet.org | The USCDI Patient Demographics Data Class requires following the Project US@ Technical Specification for Patient Addresses Final Version 1.0 for patient addresses. For new and updated records, Certifying Systems SHALL and non-Certifying Systems SHOULD follow it as the standard style guide for Patient addresses. |
| web | asapnet.org |
*
Systems SHOULD
follow the Project US@ Technical Specification for Patient Addresses Final Version 1.0
as the standard style guide for Practitioner.address.line
and Practitioner.address.city
.
|
| web | ihe.net | The US Core PractionerRole Profile inherits from the FHIR PractionerRole 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 PractionerRole Profile inherits from the FHIR PractionerRole 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 | browser.ihtsdotools.org |
QuestionnaireAnswerCodes
(a valid code from SNOMED CT
) http://hl7.org/fhir/ValueSet/questionnaire-answers
from the FHIR Standard
|
| web | asapnet.org |
*
Systems SHOULD
follow the Project US@ Technical Specification for Patient Addresses Final Version 1.0
as the standard style guide for RelatedPerson.address.line
and RelatedPerson.address.city
.
|
| 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 | ucum.org |
UnitsOfMeasureCaseSensitive
(a valid code from UCUM
) http://terminology.hl7.org/ValueSet/v3-UnitsOfMeasureCaseSensitive
|
| web | snomed.info | providing a more specific code, for example, the more specific LOINC, "75779-9 (Thoughts on cardiopulmonary resuscitation (CPR) [Reported])" , a SNOMED CT concept, or a system-specific code |
| web | www.iso.org | Copyright/Legal : ISO Maintains the copyright on the country codes and controls it's use carefully. For further details, see the ISO 3166 Home Page |
| web | snomed.info | 386053000 |
| web | snomed.info | 410606002 |
| web | snomed.info | 108252007 |
| web | snomed.info | 363679005 |
| web | snomed.info | 409063005 |
| web | snomed.info | 409073007 |
| web | snomed.info | 387713003 |
| web | snomed.info | 118127007 |
| web | snomed.info | 118129005 |
| web | snomed.info | 125152006 |
| web | snomed.info | 125153001 |
| web | snomed.info | 125159002 |
| web | snomed.info | 281263003 |
| web | snomed.info | 281265005 |
| web | snomed.info | 281270003 |
| web | snomed.info | 397212007 |
| web | snomed.info | 733480003 |
| web | snomed.info | 84567002 |
| 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 Cache-Control is present in the Server response headers, the Clients SHOULD NOT
search the same data within the time stated in Cache-Control
headers.
|
| 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 | www.icd10data.com | International Classification of Diseases, 10th Revision, Procedure Coding System (ICD-10-PCS) - See ICD-10 PCS Codes for online access to codes for general information purposes. |
| web | www.ada.org | ADA |
| web | pe.usps.com | USPS |
| web | snomed.info | SNOMED |
| web | unitsofmeasure.org | UCUM |
| web | dicom.nema.org | |
| web | www.ada.org | Code on Dental Procedures and Nomenclature |
| web | www.ama-assn.org | Current Procedural Terminology (CPT®) |
| web | snomed.info | SNOMED CT (all versions) |
| web | nahdo.org | Source of Payment Typology |
| 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_Condition_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_Patient_name.png
|
|
Must_Support_Patient_telecom.png
|
|
Must_Support_Snapshot_View.png
|
|
Must_Support_vital_signs.performer.png
|
|
Provenance_HIE_Multi_Org_Device.svg
|
|
Provenance_HIE_Single_Org_Device.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-team-members.png
|
|
clinical-notes.png
|
|
clinical-tests.png
|
|
diagnostic-imaging.png
|
|
encounter.png
|
|
facility-information.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
|
|
observation.png
|
|
orders.png
|
|
patient-demographics.png
|
|
patient-summary-and-plan.png
|
|
problems.png
|
|
procedures.png
|
|
provenance.png
|
|
screening_and_assessments.svg
|
|
sdoh_condition.svg
|
|
uscore-observation-assessment-structure.svg
|
|
vital-signs.png
|
|
vsac-1.png
|
|
vsac-2.png
|
|
vsac-3.png
|
|
yearly-updates.png
|