Health eData 1 Sandbox - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Home

Health eData Sandbox

testbed for ideas….

Example bar

showing JSON example from examples folder. Note that the narrative section renders poorly and should not be used if displaying inline examples. Use the no-narrative IG parameter to do this.

Example

{
  "resourceType" : "Patient",
  "id" : "deceased-example",
  "meta" : {
    "extension" : [{
      "url" : "http://hl7.org/fhir/StructureDefinition/instance-name",
      "valueString" : "Deceased Patient Example"
    },
    {
      "url" : "http://hl7.org/fhir/StructureDefinition/instance-description",
      "valueMarkdown" : "This is a deceased patient example for the *US Core Patient Profile*."
    }],
    "profile" : ["http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient|0.1.0"]
  },
  "text" : {
    "status" : "extensions",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n\n  <p>\n    <strong>resourceType:</strong>\n    </p>\n  <p>\n    <strong>id:</strong>\n    deceased-example</p>\n\n</div>"
  },
  "extension" : [{
    "extension" : [{
      "url" : "ombCategory",
      "valueCoding" : {
        "system" : "urn:oid:2.16.840.1.113883.6.238",
        "code" : "2106-3",
        "display" : "White"
      }
    },
    {
      "url" : "ombCategory",
      "valueCoding" : {
        "system" : "urn:oid:2.16.840.1.113883.6.238",
        "code" : "2028-9",
        "display" : "Asian"
      }
    },
    {
      "url" : "text",
      "valueString" : "Mixed"
    }],
    "url" : "http://hl7.org/fhir/us/core/StructureDefinition/us-core-race"
  },
  {
    "extension" : [{
      "url" : "ombCategory",
      "valueCoding" : {
        "system" : "urn:oid:2.16.840.1.113883.6.238",
        "code" : "2186-5",
        "display" : "Not Hispanic or Latino"
      }
    },
    {
      "url" : "text",
      "valueString" : "Not Hispanic or Latino"
    }],
    "url" : "http://hl7.org/fhir/us/core/StructureDefinition/us-core-ethnicity"
  }],
  "identifier" : [{
    "use" : "usual",
    "type" : {
      "coding" : [{
        "system" : "http://terminology.hl7.org/CodeSystem/v2-0203",
        "code" : "MR",
        "display" : "Medical Record Number"
      }],
      "text" : "Medical Record Number"
    },
    "system" : "http://hospital.smarthealthit.org",
    "value" : "55555555"
  }],
  "active" : true,
  "name" : [{
    "family" : "Shaw",
    "given" : ["Mary",
    "A."]
  }],
  "telecom" : [{
    "system" : "phone",
    "value" : "555-555-5555",
    "use" : "home"
  },
  {
    "system" : "email",
    "value" : "mary.shaw@example.com"
  }],
  "gender" : "female",
  "birthDate" : "1937-10-21",
  "deceasedDateTime" : "2022-07-22",
  "address" : [{
    "line" : ["49 Meadow St"],
    "city" : "Mounds",
    "state" : "OK",
    "postalCode" : "74047",
    "country" : "US",
    "period" : {
      "start" : "2016-12-06"
    }
  }]
}

showing XML example in images sub-folder images/inline_examples . Note that the file name is used as an id parameter in the html so they must be unique within a page.:

Example

<?xml version="1.0" encoding="UTF-8"?>

<Patient xmlns="http://hl7.org/fhir">
  <id value="deceased-example"/>
  <meta>
    <extension url="http://hl7.org/fhir/StructureDefinition/instance-name">
      <valueString value="Deceased Patient Example"/>
    </extension>
    <extension url="http://hl7.org/fhir/StructureDefinition/instance-description">
      <valueMarkdown value="This is a deceased patient example for the *US Core Patient Profile*."/>
    </extension>
    <profile value="http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient|0.1.0"/>
  </meta>
  <text>
    <status value="extensions"/><div xmlns="http://www.w3.org/1999/xhtml">

  <p>
    <strong>resourceType:</strong>
    </p>
  <p>
    <strong>id:</strong>
    deceased-example</p>

</div>
  </text>
  <extension url="http://hl7.org/fhir/us/core/StructureDefinition/us-core-race">
    <extension url="ombCategory">
      <valueCoding>
        <system value="urn:oid:2.16.840.1.113883.6.238"/>
        <code value="2106-3"/>
        <display value="White"/>
      </valueCoding>
    </extension>
    <extension url="ombCategory">
      <valueCoding>
        <system value="urn:oid:2.16.840.1.113883.6.238"/>
        <code value="2028-9"/>
        <display value="Asian"/>
      </valueCoding>
    </extension>
    <extension url="text">
      <valueString value="Mixed"/>
    </extension>
  </extension>
  <extension url="http://hl7.org/fhir/us/core/StructureDefinition/us-core-ethnicity">
    <extension url="ombCategory">
      <valueCoding>
        <system value="urn:oid:2.16.840.1.113883.6.238"/>
        <code value="2186-5"/>
        <display value="Not Hispanic or Latino"/>
      </valueCoding>
    </extension>
    <extension url="text">
      <valueString value="Not Hispanic or Latino"/>
    </extension>
  </extension>
  <identifier>
    <use value="usual"/>
    <type>
      <coding>
        <system value="http://terminology.hl7.org/CodeSystem/v2-0203"/>
        <code value="MR"/>
        <display value="Medical Record Number"/>
      </coding>
      <text value="Medical Record Number"/>
    </type>
    <system value="http://hospital.smarthealthit.org"/>
    <value value="55555555"/>
  </identifier>
  <active value="true"/>
  <name>
    <family value="Shaw"/>
    <given value="Mary"/>
    <given value="A."/>
  </name>
  <telecom>
    <system value="phone"/>
    <value value="555-555-5555"/>
    <use value="home"/>
  </telecom>
  <telecom>
    <system value="email"/>
    <value value="mary.shaw@example.com"/>
  </telecom>
  <gender value="female"/>
  <birthDate value="1937-10-21"/>
  <deceasedDateTime value="2022-07-22"/>
  <address>
    <line value="49 Meadow St"/>
    <city value="Mounds"/>
    <state value="OK"/>
    <postalCode value="74047"/>
    <country value="US"/>
    <period>
      <start value="2016-12-06"/>
    </period>
  </address>
</Patient>

See the guidance page for how to render code snippets from examples

FOO

using http:

​US Core

FHIR

using https:

US Core

FHIR

using path variable

FHIR

in list…:

using http:

• ​US Core
• FHIR

using https:

• US Core
• FHIR

in table…:

using http:

using https:

Cross Version Analysis<p>This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 (healthedata1-sandbox.r4) and R4B (healthedata1-sandbox.r4b) are available.</p>

bar This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 (healthedata1-sandbox.r4) and R4B (healthedata1-sandbox.r4b) are available. foo

IG Dependencies

This IG Contains the following dependencies on other IGs.<div><table border="0" cellpadding="0" cellspacing="0" style="border: 0px #F0F0F0 solid; font-size: 11px; font-family: verdana; vertical-align: top;"><tr style="border: 1px #F0F0F0 solid; font-size: 11px; font-family: verdana; vertical-align: top"><th style="vertical-align: top; text-align : left; background-color: white; border: 0px #F0F0F0 solid; padding:0px 4px 0px 4px" class="hierarchy">IG</th><th style="vertical-align: top; text-align : left; background-color: white; border: 0px #F0F0F0 solid; padding:0px 4px 0px 4px" class="hierarchy">Package</th><th style="vertical-align: top; text-align : left; background-color: white; border: 0px #F0F0F0 solid; padding:0px 4px 0px 4px" class="hierarchy">FHIR</th><th style="vertical-align: top; text-align : left; background-color: white; border: 0px #F0F0F0 solid; padding:0px 4px 0px 4px" class="hierarchy">Comment</th></tr><tr style="border: 0px #F0F0F0 solid; padding:0px; vertical-align: top; background-color: white"><td style="vertical-align: top; text-align : left; background-color: white; border: 0px #F0F0F0 solid; padding:0px 4px 0px 4px; white-space: nowrap; background-image: url(/home/runner/work/Healthedata1-Sandbox/Healthedata1-Sandbox/temp/pagesdata:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAyAAAAACCAYAAACg/LjIAAAALUlEQVR4Xu3IoREAIAwEwfT6/ddA0GBAxO3NrLlKUj9263wAAAAvrgEAADClAVWFQIBRHMicAAAAAElFTkSuQmCC)" class="hierarchy"> Health eData 1 Sandbox</td><td style="vertical-align: top; text-align : left; background-color: white; border: 0px #F0F0F0 solid; padding:0px 4px 0px 4px" class="hierarchy">healthedata1-sandbox#0.1.0</td><td style="vertical-align: top; text-align : left; background-color: white; border: 0px #F0F0F0 solid; padding:0px 4px 0px 4px" class="hierarchy">R4</td><td style="vertical-align: top; text-align : left; background-color: white; border: 0px #F0F0F0 solid; padding:0px 4px 0px 4px" class="hierarchy"></td></tr>

</table></div><table class="grid"><tr><td><p>Package hl7.fhir.uv.extensions.r4#1.0.0</p>

This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00)

</td></tr></table><table class="grid"><tr><td><p>Package hl7.fhir.uv.bulkdata#2.0.0</p>

FHIR based approach for exporting large data sets from a FHIR server to a client application (built Fri, Nov 26, 2021 05:56+1100+11:00)

</td></tr></table><table class="grid"><tr><td><p>Package hl7.fhir.r4.examples#4.0.1</p>

Example resources in the R4 version of the FHIR standard

</td></tr></table><table class="grid"><tr><td><p>Package hl7.fhir.uv.sdc#3.0.0</p>

The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR.
This includes two components:
* Support more sophisticated questionnaire/form use-cases such as those needed for research, oncology, pathology and other clinical domains.
*Support pre-population and auto-population of EHR data into forms/questionnaires for uses outside direct clinical care (patient safety, adverse event reporting, public health reporting, etc.). (built Tue, Mar 8, 2022 18:32+0000+00:00)

</td></tr></table><table class="grid"><tr><td><p>Package hl7.fhir.us.core#5.0.1</p>

The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum conformance requirements for accessing patient data. The Argonaut pilot implementations, ONC 2015 Edition Common Clinical Data Set (CCDS), and ONC U.S. Core Data for Interoperability (USCDI) v1 provided the requirements for this guide. The prior Argonaut search and vocabulary requirements, based on FHIR DSTU2, are updated in this guide to support FHIR Version R4. This guide was used as the basis for further testing and guidance by the Argonaut Project Team to provide additional content and guidance specific to Data Query Access for purpose of ONC Certification testing. These profiles are the foundation for future US Realm FHIR implementation guides. In addition to Argonaut, they are used by DAF-Research, QI-Core, and CIMI. Under the guidance of HL7 and the HL7 US Realm Steering Committee, the content will expand in future versions to meet the needs specific to the US Realm. These requirements were originally developed, balloted, and published in FHIR DSTU2 as part of the Office of the National Coordinator for Health Information Technology (ONC) sponsored Data Access Framework (DAF) project. For more information on how DAF became US Core see the US Core change notes. (built Wed, Jun 22, 2022 19:44+0000+00:00)

</td></tr></table>

Global Profiles

There are no Global profiles defined

Copyrights

  This publication includes IP covered under the following statements.
<ul>
<li>Copyright HL7. Licensed under creative commons public domain<div id="ipp_1" onClick="if (document.getElementById('ipp2_1').innerHTML != '') {document.getElementById('ipp_1').innerHTML = document.getElementById('ipp2_1').innerHTML; document.getElementById('ipp2_1').innerHTML = ''}"> <span style="cursor: pointer; border: 1px grey solid; background-color: #fcdcb3; padding-left: 3px; padding-right: 3px; color: black">Show Usage</span></div><div id="ipp2_1" style="display: none">
<ul>
<li><a href="http://terminology.hl7.org/5.3.0/CodeSystem-v2-0203.html">identifierType</a>: <a href="Patient-deceased-example.html">Patient/deceased-example</a></li>
</ul>
</div></li>
<li>Most of the information on the CDC and ATSDR websites is not subject to copyright, is in the public domain, and may be freely used or reproduced without obtaining copyright permission.For information and exceptions regarding use of CDC material please see <a href="https://www.cdc.gov/other/agencymaterials.html">https://www.cdc.gov/other/agencymaterials.html</a>.<div id="ipp_2" onClick="if (document.getElementById('ipp2_2').innerHTML != '') {document.getElementById('ipp_2').innerHTML = document.getElementById('ipp2_2').innerHTML; document.getElementById('ipp2_2').innerHTML = ''}"> <span style="cursor: pointer; border: 1px grey solid; background-color: #fcdcb3; padding-left: 3px; padding-right: 3px; color: black">Show Usage</span></div><div id="ipp2_2" style="display: none">
<ul>
<li><a href="http://terminology.hl7.org/3.1.0/CodeSystem-CDCREC.html">CDC Race and Ethnicity</a>: <a href="Patient-deceased-example.html">Patient/deceased-example</a> and <a href="Patient-example-targeted-provenance.html">Patient/example-targeted-provenance</a></li>
</ul>
</div></li>
<li>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. <a href="https://ucum.org/trac/wiki/TermsOfUse">https://ucum.org/trac/wiki/TermsOfUse</a><div id="ipp_3" onClick="if (document.getElementById('ipp2_3').innerHTML != '') {document.getElementById('ipp_3').innerHTML = document.getElementById('ipp2_3').innerHTML; document.getElementById('ipp2_3').innerHTML = ''}"> <span style="cursor: pointer; border: 1px grey solid; background-color: #fcdcb3; padding-left: 3px; padding-right: 3px; color: black">Show Usage</span></div><div id="ipp2_3" style="display: none">
<ul>
<li><a href="http://terminology.hl7.org/3.1.0/CodeSystem-v3-ucum.html">Unified Code for Units of Measure (UCUM)</a>: <a href="StructureDefinition-us-core-vital-signs.html">USCoreVitalSignsProfile</a></li>
</ul>
</div></li>
<li>These codes are excerpted from Digital Imaging and Communications in Medicine (DICOM) Standard, Part 16: Content Mapping Resource, Copyright &copy; 2011 by the National Electrical Manufacturers Association.<div id="ipp_4" onClick="if (document.getElementById('ipp2_4').innerHTML != '') {document.getElementById('ipp_4').innerHTML = document.getElementById('ipp2_4').innerHTML; document.getElementById('ipp2_4').innerHTML = ''}"> <span style="cursor: pointer; border: 1px grey solid; background-color: #fcdcb3; padding-left: 3px; padding-right: 3px; color: black">Show Usage</span></div><div id="ipp2_4" style="display: none">
<ul>
<li><a href="http://hl7.org/fhir/R4/codesystem-dicom-dcim.html">DICOM Controlled Terminology Definitions</a>: <a href="Provenance-example-targeted-provenance.html">Provenance/example-targeted-provenance</a></li>
</ul>
</div></li>
<li>This material contains content from <a href="http://loinc.org">LOINC</a>. LOINC is copyright © 1995-2020, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the <a href="http://loinc.org/license">license</a>. LOINC® is a registered United States trademark of Regenstrief Institute, Inc.<div id="ipp_5" onClick="if (document.getElementById('ipp2_5').innerHTML != '') {document.getElementById('ipp_5').innerHTML = document.getElementById('ipp2_5').innerHTML; document.getElementById('ipp2_5').innerHTML = ''}"> <span style="cursor: pointer; border: 1px grey solid; background-color: #fcdcb3; padding-left: 3px; padding-right: 3px; color: black">Show Usage</span></div><div id="ipp2_5" style="display: none">
<ul>
<li><a href="http://terminology.hl7.org/5.3.0/CodeSystem-v3-loinc.html">LOINC</a>: <a href="StructureDefinition-us-core-blood-pressure.html">USCoreBloodPressureProfile</a>, <a href="StructureDefinition-pediatric-bmi-for-age.html">USCorePediatricBMIforAgeObservationProfile</a>, <a href="StructureDefinition-pediatric-weight-for-height.html">USCorePediatricWeightForHeightObservationProfile</a> and <a href="StructureDefinition-us-core-vital-signs.html">USCoreVitalSignsProfile</a></li>
</ul>
</div></li>
<li>This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact <a href="https://www.snomed.org/get-snomed">https://www.snomed.org/get-snomed</a> or <a href="mailto:info@snomed.org">info@snomed.org</a>.<div id="ipp_6" onClick="if (document.getElementById('ipp2_6').innerHTML != '') {document.getElementById('ipp_6').innerHTML = document.getElementById('ipp2_6').innerHTML; document.getElementById('ipp2_6').innerHTML = ''}"> <span style="cursor: pointer; border: 1px grey solid; background-color: #fcdcb3; padding-left: 3px; padding-right: 3px; color: black">Show Usage</span></div><div id="ipp2_6" style="display: none">
<ul>
<li><a href="http://hl7.org/fhir/R4/codesystem-snomedct.html">SNOMED Clinical Terms® (SNOMED CT®)</a>: <a href="StructureDefinition-us-core-allergyintolerance.html">USCoreAllergyIntolerance</a></li>
</ul>
</div></li>
<li>Using RxNorm codes of type SAB=RXNORM as this specification describes does not require  a UMLS license. Access to the full set of RxNorm definitions, and/or additional use of other RxNorm structures and information requires a UMLS license. The use of RxNorm in this specification is pursuant to HL7's status as a licensee of the NLM UMLS. HL7's license does not convey the right to use RxNorm to any users of this specification; implementers must acquire a license to use RxNorm in their own right.<div id="ipp_7" onClick="if (document.getElementById('ipp2_7').innerHTML != '') {document.getElementById('ipp_7').innerHTML = document.getElementById('ipp2_7').innerHTML; document.getElementById('ipp2_7').innerHTML = ''}"> <span style="cursor: pointer; border: 1px grey solid; background-color: #fcdcb3; padding-left: 3px; padding-right: 3px; color: black">Show Usage</span></div><div id="ipp2_7" style="display: none">
<ul>
<li><a href="http://terminology.hl7.org/3.1.0/CodeSystem-v3-rxNorm.html">RxNorm</a>: <a href="StructureDefinition-us-core-allergyintolerance.html">USCoreAllergyIntolerance</a></li>
</ul>
</div></li>
</ul>
<!--$$1$$-->

This publication includes IP covered under the following statements.

• Copyright HL7. Licensed under creative commons public domain
  Show Usage
  • identifierType: Patient/deceased-example
• Most of the information on the CDC and ATSDR websites is not subject to copyright, is in the public domain, and may be freely used or reproduced without obtaining copyright permission.For information and exceptions regarding use of CDC material please see https://www.cdc.gov/other/agencymaterials.html.
  Show Usage
  • CDC Race and Ethnicity: Patient/deceased-example and Patient/example-targeted-provenance
• 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
  • Unified Code for Units of Measure (UCUM): USCoreVitalSignsProfile
• These codes are excerpted from Digital Imaging and Communications in Medicine (DICOM) Standard, Part 16: Content Mapping Resource, Copyright © 2011 by the National Electrical Manufacturers Association.
  Show Usage
  • DICOM Controlled Terminology Definitions: Provenance/example-targeted-provenance
• This material contains content from LOINC. LOINC is copyright © 1995-2020, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc.
  Show Usage
  • LOINC: USCoreBloodPressureProfile, USCorePediatricBMIforAgeObservationProfile, USCorePediatricWeightForHeightObservationProfile and USCoreVitalSignsProfile
• This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/get-snomed or info@snomed.org.
  Show Usage
  • SNOMED Clinical Terms® (SNOMED CT®): USCoreAllergyIntolerance
• Using RxNorm codes of type SAB=RXNORM as this specification describes does not require a UMLS license. Access to the full set of RxNorm definitions, and/or additional use of other RxNorm structures and information requires a UMLS license. The use of RxNorm in this specification is pursuant to HL7's status as a licensee of the NLM UMLS. HL7's license does not convey the right to use RxNorm to any users of this specification; implementers must acquire a license to use RxNorm in their own right.
  Show Usage
  • RxNorm: USCoreAllergyIntolerance

using

{{ site.data.resources[resource_].description }}

by string

with markdown filter

This is a Healthedata1 sandbox for creation of resources and examples

without markdown filter

This is a Healthedata1 sandbox for creation of resources and examples

0: John

1: Paul

2: George

3: Ringo

Using Groupby Jekyll Liquid

a simple csv in data to a fancy table in html

US Core Data for Interoperability USCD V3

Allergies and Intolerances	​ US Core AllergyIntolerance Profile	​See Foooooooooo Barrrrrr
•Substance (Medication)	​ US Core AllergyIntolerance Profile
•Substance (Drug Class)	​ US Core AllergyIntolerance Profile
•Reaction	​ US Core AllergyIntolerance Profile

Assessment and Plan of Treatment	​ US Core CarePlan Profile US Core Simple Observation Profile US Core Observation Screening Assessment Profile US Core QuestionnaireResponse Profile
•Assessment and Plan of Treatment	​ US Core CarePlan Profile
•SDOH Assessment	​ US Core Simple Observation Profile US Core Condition Problems and Health Concerns Profile US Core Observation Screening Assessment Profile US Core QuestionnaireResponse Profile	​ See Screening and Assessments Guidance

Care Team Members	​ US Core CareTeam Profile
•Name	​ US Core CareTeam Profile
•Identifier	​ US Core CareTeam Profile
•Location	​ US Core CareTeam Profile
•Telecom	​ US Core CareTeam Profile
•Role	​ US Core CareTeam Profile

Clinical Notes	​ US Core DocumentReference Profile US Core DiagnosticReport Profile for Report and Note Exchange
•Consultation Note	​ US Core DocumentReference Profile
•Discharge Summary Note	​ US Core DocumentReference Profile
•History & Physical	​ US Core DocumentReference Profile
•Imaging Narrative	​ US Core DocumentReference Profile US Core DiagnosticReport Profile for Report and Note Exchange
•Laboratory Report Narrative	​ US Core DocumentReference Profile US Core DiagnosticReport Profile for Report and Note Exchange
•Pathology Report Narrative	​ US Core DocumentReference Profile US Core DiagnosticReport Profile for Report and Note Exchange
•Procedure Note	​ US Core DocumentReference Profile US Core DiagnosticReport Profile for Report and Note Exchange
•Progress Note	​ US Core DocumentReference Profile	​ See Clinical Notes Guidance

Clinical Tests	​ US Core Observation Clinical Result Profile US Core DiagnosticReport Profile for Report and Note Exchange
•Clinical Test	​ US Core Observation Clinical Result Profile US Core DiagnosticReport Profile for Report and Note Exchange
•Clinical Test Result/Report	​ US Core Observation Clinical Result Profile US Core DiagnosticReport Profile for Report and Note Exchange

Diagnostic Imaging	​ US Core Observation Clinical Result Profile US Core DiagnosticReport Profile for Report and Note Exchange
•Diagnostic Imaging Test	​ US Core Observation Clinical Result Profile US Core DiagnosticReport Profile for Report and Note Exchange
•Diagnostic Imaging Result/Report	​ US Core Observation Clinical Result Profile US Core DiagnosticReport Profile for Report and Note Exchange

Encounter	​ US Core Encounter Profile
•Type	​ US Core Encounter Profile
•Diagnosis	​ US Core Condition Encounter Diagnosis Profile
•Time	​ US Core Encounter Profile
•Location	​ US Core Encounter Profile
•Disposition	​ US Core Encounter Profile

Goals	​ US Core Goal Profile
•Patient Goals	​ US Core Goal Profile
•SDOH Goals	​ US Core Goal Profile	​ See Screening and Assessments Guidance

Health Insurance Information	​ US Core Coverage Profile
•Coverage Status	​ US Core Coverage Profile
•Coverage Type	​ US Core Coverage Profile
•Relationship to Subscriber	​ US Core Coverage Profile
•Member Identifier	​ US Core Coverage Profile
•Subscriber Identifier	​ US Core Coverage Profile
•Group Number	​ US Core Coverage Profile
•Payer Identifier	​ US Core Coverage Profile

Health Status/Assessments	​ US Core Simple Observation Profile US Core Condition Problems and Health Concerns Profile US Core Observation Screening Assessment Profile US Core QuestionnaireResponse Profile
•Health Concerns	​ US Core Condition Problems and Health Concerns Profile
•Functional Status	​ US Core Simple Observation Profile US Core Condition Problems and Health Concerns Profile US Core Observation Screening Assessment Profile US Core QuestionnaireResponse Profile	​ See Screening and Assessments Guidance
•Disability Status	​ US Core Simple Observation Profile US Core Condition Problems and Health Concerns Profile US Core Observation Screening Assessment Profile US Core QuestionnaireResponse Profile
•Mental/Cognitive Status	​ US Core Simple Observation Profile US Core Condition Problems and Health Concerns Profile US Core Observation Screening Assessment Profile US Core QuestionnaireResponse Profile
•Pregnancy Status	​ US Core Observation Pregnancy Status Profile US Core Observation Pregnancy Intent Profile
•Smoking Status	​ US Core Smoking Status Observation Profile

Immunizations	​ US Core Immunization Profile
•	​ US Core Immunization Profile

Laboratory	​ US Core Laboratory Result Observation Profile US Core DiagnosticReport Profile for Laboratory Results Reporting US Core Specimen Profile
•Tests	​ US Core Laboratory Result Observation Profile US Core DiagnosticReport Profile for Laboratory Results Reporting
•Values/Results	​ US Core Laboratory Result Observation Profile US Core DiagnosticReport Profile for Laboratory Results Reporting
•Specimen Type	​ US Core Laboratory Result Observation Profile US Core Specimen Profile
•Result Status	​ US Core Laboratory Result Observation Profile US Core DiagnosticReport Profile for Laboratory Results Reporting

Medications	​ US Core MedicationRequest Profile US Core MedicationDispense Profile US Core Medication Profile
•Medications	​ US Core Medication Profile US Core Medication Request Profile	​ See Medication List Guidance
•Dose	​ US Core Medication Request Profile
•Dose Unit of Measure	​ US Core Medication Request Profile
•Indication	​ US Core Medication Request Profile
•Fill Status	​ US Core Medication Dispense Profile

Patient Demographics	​ US Core Patient Profile US Core Observation Sexual Orientation Profile US Core Observation Sexual Orientation Profile US Core Observation Sexual Orientation Profile US Core Observation Occupation Profile
•First Name	​ US Core Patient Profile
•Last Name	​ US Core Patient Profile
•Previous Name	​ US Core Patient Profile
•Middle Name (including middle initial)	​ US Core Patient Profile
•Suffix	​ US Core Patient Profile
•Birth Sex	​ US Core Patient Profile US Core Birth Sex Extension
•Sex	​ US Core Patient Profile US Core Birth Sex Extension
•Date of Birth	​ US Core Patient Profile
•Date of Death	​ US Core Patient Profile
•Race	​ US Core Race Extension
•Ethnicity	​ US Core Patient Profile US Core Ethnicity Extension
•Tribal Affiliation	​ US Core Patient Profile US Core Tribal Affiliation Extension
•Gender Identity	​ US Core Patient Profile US Core Gender Identity Extension
•Sexual Orientation	​ US Core Observation Sexual Orientation Profile
•Preferred Language	​ US Core Patient Profile
•Address	​ US Core Patient Profile
•Previous Address	​ US Core Patient Profile
•Email	​ US Core Patient Profile
•Phone Number	​ US Core Patient Profile
•Related Person's Name	​ US Core RelatedPerson Profile
•Related Person's Relationship	​ US Core RelatedPerson Profile
•Occupation	​ US Core Observation Occupation Profile
•Occupation Industry	​ US Core Observation Occupation Profile

Problems	​ US Core Condition Problems and Health Concerns Profile
•Date of Resolution	​ US Core Condition Problems and Health Concerns Profile
•Date of Diagnosis	​ US Core Condition Problems and Health Concerns Profile
•SDOH Problems/Health Concerns	​ US Core Condition Problems and Health Concerns Profile	​ See Screening and Assessments Guidance

Procedures	​ US Core Procedure Profile US Core ServiceRequest Profile
•Procedure	​ US Core Procedure Profile
•Reason for Referral	​ US Core ServiceRequest Profile
•SDOH Interventions	​ US Core ServiceRequest Profile US Core Procedure Profile	​ See Screening and Assessments Guidance

Provenance	​ US Core Provenance Profile	​See Basic Provenance Guidance
•Author Time Stamp	​ US Core Provenance Profile
•Author Organization	​ US Core Provenance Profile

Unique Device Identifier(s)	​ US Core Implantable Device Profile
•Unique Device Identifier(s) for a Patient's Implantable Device(s)	​ US Core Implantable Device Profile

Vital Signs	​ US Core Vital Signs Profile
•Diastolic blood pressure	​ US Core Blood Pressure Profile
•Systolic blood pressure	​ US Core Blood Pressure Profile
•Body height	​ US Core Body Height Profile
•Body weight	​ US Core Body Weight Profile
•Heart rate	​ US Core Heart Rate Profile
•Respiratory rate	​ US Core Respiratory Rate Profile
•Body temperature	​ US Core Body Temperature Profile
•Pulse oximetry	​ US Core Pulse Oximetry Profile
•Inhaled oxygen concentration	​ US Core Pulse Oximetry Profile
•BMI Percentile (2-20 years old)	​ US Core Pediatric BMI for Age Observation Profile
•Weight-for-length Percentile (Birth - 36 months)	​ US Core Pediatric Weight for Height Observation Profile
•Occipital Frontal Head Circumference Percentile (Birth - 36 months)	​ US Core Pediatric Head Occipital Frontal Circumference Percentile Profile

publisher shortcuts …

use url to get the title an link for :

profiles : e.g., ‘ {{[http://www.fhir.org/guides/healthedata1-sandbox/StructureDefinition/argo-write-observation]}} ‘ =

what about terminology?: e.g., ‘ US Core Source of Payment Value Set ‘ = US Core Source of Payment Value Set

tabler