Merge pull request #53 from standardhealth/config_shr

Standard Health Record configuration files

spec/config.json

@@ -0,0 +1,18 @@
+{
+    "projectName": "Standard Health Record",
+    "projectShorthand": "SHR",
+    "projectURL": "http://standardhealthrecord.org",
+    "fhirURL": "http://standardhealthrecord.org/fhir",
+    "igIndexContent": "shrIndexContent.html",
+    "publisher": "The MITRE Corporation: Standard Health Record Collaborative",
+    "contact": [
+        {
+            "telecom": [
+                {
+                    "system": "url",
+                    "value": "http://standardhealthrecord.org"
+                }
+            ]
+        }
+    ]
+}

spec/shrIndexContent.html

@@ -0,0 +1,51 @@
+<p style="background-color: #ffdddd; border:1px solid maroon; padding: 5px;">
+  This is a preliminary version of the Standard Health Record (SHR) Health Level 7 (HL7) Fast Healthcare
+  Interoperability Resources (FHIR) profiles, extensions, value sets, and code systems.<br/>
+  For more information see the <a href="http://standardhealthrecord.org">Standard Health Record
+  Collaborative <img style="text-align: baseline" src="external.png" /></a>.
+</p>
+<h2>Standard Health Record Implementation Guide (IG)</h2>
+<p>
+  The Standard Health Record (SHR) provides a high quality, computable source of patient information by
+  establishing a single target for health data standardization. The SHR is foundational, dealing first with the
+  reliable and repeatable collection and aggregation of a wide range of patient-focused data. Through the SHR, we
+  realize greater transparency, empowerment, and clinical interoperability that supports patients, caregivers,
+  clinicians, researchers, scientists, and public health organizations.
+</p>
+<p>
+  Enabled through open source technology, the SHR is designed by, and for, its users to support communication
+  across homes and healthcare systems. The SHR enables organizations, and the American public, to realize the
+  benefits of improved care communication and coordination, reductions in medical errors, less waste, fraud, and
+  abuse, enhanced information sharing, and the decreased costs that accompany a large-scale focus on prevention.
+</p>
+<p>
+  This Implementation Guide defines FHIR profiles, extensions, value sets, and code systems necessary to exchange
+  SHR elements using FHIR 3.0.1 (a.k.a. STU3). Many elements and fields in SHR do not have direct
+  equivalents in FHIR. Where possible, SHR element fields have been mapped to existing FHIR properties. When it is
+  not possible to map a field to a property, an extension is defined. In the spirit of re-usability, extensions
+  are defined globally and referenced wherever they are needed.
+</p>
+<h3>Known Issues and Limitations</h3>
+<p>
+  HL7 FHIR and the Standard Health Record Collaborative are continually evolving works-in-progress.  These
+  profiles use FHIR 3.0.1 (a.k.a. STU3), which is a pre-cursor to the final FHIR Normative release.  The content
+  of the profiles is based on the latest SHR data element definitions as of the publish date. HL7 FHIR, the SHR,
+  and the SHR HL7 FHIR Profiles will all continue to evolve.
+</p>
+<p>
+  The following are known issues and limitations as these specifications continue to evolve:
+  <ul>
+    <li>These profiles are not yet fully compatibile with US-Core.  Future versions will improve compatibility,
+      with the goal that data conforming to SHR profiles will also conform to corresponding US-Core profiles.</li>
+    <li>These profiles are generated from formal SHR data element definitions and mappings.  While it is a goal
+      to explicitly map every SHR-defined entry element to FHIR, a small number have not yet been mapped and are
+      temporarily profiled on FHIR's Basic resource.
+    <li>The terminology server used to expand value sets does not support all value sets and code systems used by
+      SHR.  Value set documentation will indicate when this occurs.</li>
+    <li>The Implementation Guide publisher incorrectly renders some characters and links, occasionally causing
+      broken links to external content.  This is a known bug in the FHIR IG publishing tool.</li>
+    <li>In some cases, deeply nested SHR data elements are not fully represented in detail in FHIR profiles.
+      While the core data is always represented, there are ongoing discussions to determine how best to represent
+      the more detailed qualifying elements of deeply nested structures.</li>
+  </ul>
+</p>