add mockup for lastUpdated in Observation

fsh-generated/includes/fsh-link-references.md

@@ -1,5 +1,9 @@
+[encounter-diagnosis-example3]: Condition-encounter-diagnosis-example3.html
 [encounter-diagnosis-example1]: Condition-encounter-diagnosis-example1.html
+[encounter-diagnosis-example2]: Condition-encounter-diagnosis-example2.html
+[encounter-diagnosis-example4]: Condition-encounter-diagnosis-example4.html
+[serum-bun]: Observation-serum-bun.html
 [USCoreCommonSDOHAssessments]: ValueSet-uscore-common-sdoh-assessments.html
 [USCoreConditionEncounterDiagnosisProfile]: StructureDefinition-us-core-condition-encounter-diagnosis.html
-[USCorePatientProfile]: StructureDefinition-us-core-patient.html
-[UsCoreServerCapabilityStatement]: CapabilityStatement-us-core-server.html
+[USCoreLaboratoryResultObservationProfile]: StructureDefinition-us-core-observation-lab.html
+[USCorePatientProfile]: StructureDefinition-us-core-patient.html

fsh-generated/resources/ImplementationGuide-uscdi4-sandbox.json

@@ -59,6 +59,14 @@
   ],
   "definition": {
     "resource": [
+      {
+        "reference": {
+          "reference": "Condition/encounter-diagnosis-example3"
+        },
+        "description": "This example of a US Core Condition Encounter Diagnosis Profile illustrates its use to capture information about a patient's encounter diagnosis.",
+        "name": "Encounter Diagnosis Example 1",
+        "exampleCanonical": "http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-encounter-diagnosis"
+      },
       {
         "reference": {
           "reference": "Condition/encounter-diagnosis-example1"
@@ -67,6 +75,30 @@
         "name": "Encounter Diagnosis Example 1",
         "exampleCanonical": "http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-encounter-diagnosis"
       },
+      {
+        "reference": {
+          "reference": "Condition/encounter-diagnosis-example2"
+        },
+        "description": "This example of a US Core Condition Encounter Diagnosis Profile illustrates its use to capture information about a patient's encounter diagnosis.",
+        "name": "Encounter Diagnosis Example 1",
+        "exampleCanonical": "http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-encounter-diagnosis"
+      },
+      {
+        "reference": {
+          "reference": "Condition/encounter-diagnosis-example4"
+        },
+        "description": "This example of a US Core Condition Encounter Diagnosis Profile illustrates its use to capture information about a patient's encounter diagnosis.",
+        "name": "Encounter Diagnosis Example 1",
+        "exampleCanonical": "http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-encounter-diagnosis"
+      },
+      {
+        "reference": {
+          "reference": "Observation/serum-bun"
+        },
+        "description": "This is a BUN example for the *US Core Observation Lab Profile*.",
+        "name": "Serum BUN Example",
+        "exampleCanonical": "http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab"
+      },
       {
         "reference": {
           "reference": "ValueSet/uscore-common-sdoh-assessments"
@@ -85,19 +117,19 @@
       },
       {
         "reference": {
-          "reference": "StructureDefinition/us-core-patient"
+          "reference": "StructureDefinition/us-core-observation-lab"
         },
-        "description": "The US Core Patient Profile meets the U.S. Core Data for Interoperability (USCDI) v3 'Patient Demographics' requirements. This profile sets minimum expectations for the Patient resource to record, search, and fetch basic demographics and other administrative information about an individual patient. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource when using this profile to promote interoperability and adoption through common implementation.  It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource and constrains the way the elements are used when using this profile.  It provides the floor for standards development for specific use cases.",
+        "description": "The US Core Laboratory Result Observation Profile is based upon the US Core Observation Clinical Result Profile and, along with the US Core DiagnosticReport Profile for Laboratory Results Reporting, meets the U.S. Core Data for Interoperability (USCDI) Laboratory requirements. Laboratory results are grouped and summarized using the DiagnosticReport resource, which references Observation resources. Each Observation resource represents an individual laboratory test and result value, a “nested” panel (such as a microbial susceptibility panel) that references other observations, or rarely a laboratory test with component result values. The US Core Laboratory Result Observation Profile sets minimum expectations for the Observation resource to record, search, and fetch laboratory test results associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases.",
         "exampleBoolean": false,
-        "name": "US Core Patient Profile"
+        "name": "US Core Laboratory Result Observation Profile"
       },
       {
         "reference": {
-          "reference": "CapabilityStatement/us-core-server"
+          "reference": "StructureDefinition/us-core-patient"
         },
-        "description": "This Section describes the expected capabilities of the US Core Server actor which is responsible for providing responses to the queries submitted by the US Core Requestors. The complete list of FHIR profiles, RESTful operations, and search parameters supported by US Core Servers are defined. Systems implementing this capability statement should meet the ONC 2015 Common Clinical Data Set (CCDS) access requirement for Patient Selection 170.315(g)(7) and Application Access - Data Category Request 170.315(g)(8) and the ONC [U.S. Core Data for Interoperability (USCDI) Version 4 July 2023](https://www.healthit.gov/sites/isa/files/2023-07/Final-USCDI-Version-4-July-2023-Final.pdf).  US Core Clients have the option of choosing from this list to access necessary data based on their local use cases and other contextual requirements.",
+        "description": "The US Core Patient Profile meets the U.S. Core Data for Interoperability (USCDI) v3 'Patient Demographics' requirements. This profile sets minimum expectations for the Patient resource to record, search, and fetch basic demographics and other administrative information about an individual patient. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource when using this profile to promote interoperability and adoption through common implementation.  It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource and constrains the way the elements are used when using this profile.  It provides the floor for standards development for specific use cases.",
         "exampleBoolean": false,
-        "name": "US Core Server CapabilityStatement"
+        "name": "US Core Patient Profile"
       }
     ],
     "page": {

input/data/ig.yml

@@ -36,12 +36,35 @@ dependsOn:
   id: hl7_fhir_uv_extensions_r4
 definition:
   resource:
+  - reference:
+      reference: Condition/encounter-diagnosis-example3
+    description: This example of a US Core Condition Encounter Diagnosis Profile illustrates
+      its use to capture information about a patient's encounter diagnosis.
+    name: Encounter Diagnosis Example 1
+    exampleCanonical: http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-encounter-diagnosis
   - reference:
       reference: Condition/encounter-diagnosis-example1
     description: This example of a US Core Condition Encounter Diagnosis Profile illustrates
       its use to capture information about a patient's encounter diagnosis.
     name: Encounter Diagnosis Example 1
     exampleCanonical: http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-encounter-diagnosis
+  - reference:
+      reference: Condition/encounter-diagnosis-example2
+    description: This example of a US Core Condition Encounter Diagnosis Profile illustrates
+      its use to capture information about a patient's encounter diagnosis.
+    name: Encounter Diagnosis Example 1
+    exampleCanonical: http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-encounter-diagnosis
+  - reference:
+      reference: Condition/encounter-diagnosis-example4
+    description: This example of a US Core Condition Encounter Diagnosis Profile illustrates
+      its use to capture information about a patient's encounter diagnosis.
+    name: Encounter Diagnosis Example 1
+    exampleCanonical: http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-encounter-diagnosis
+  - reference:
+      reference: Observation/serum-bun
+    description: This is a BUN example for the *US Core Observation Lab Profile*.
+    name: Serum BUN Example
+    exampleCanonical: http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab
   - reference:
       reference: ValueSet/uscore-common-sdoh-assessments
     description: "Common SDOH assessment concepts covering the following categories\
@@ -67,6 +90,26 @@ definition:
       profile. It provides the floor for standards development for specific use cases.
     exampleBoolean: false
     name: US Core Condition Encounter Diagnosis Profile
+  - reference:
+      reference: StructureDefinition/us-core-observation-lab
+    description: "The US Core Laboratory Result Observation Profile is based upon\
+      \ the US Core Observation Clinical Result Profile and, along with the US Core\
+      \ DiagnosticReport Profile for Laboratory Results Reporting, meets the U.S.\
+      \ Core Data for Interoperability (USCDI) Laboratory requirements. Laboratory\
+      \ results are grouped and summarized using the DiagnosticReport resource, which\
+      \ references Observation resources. Each Observation resource represents an\
+      \ individual laboratory test and result value, a \u201Cnested\u201D panel (such\
+      \ as a microbial susceptibility panel) that references other observations, or\
+      \ rarely a laboratory test with component result values. The US Core Laboratory\
+      \ Result Observation Profile sets minimum expectations for the Observation resource\
+      \ to record, search, and fetch laboratory test results associated with a patient\
+      \ to promote interoperability and adoption through common implementation. It\
+      \ identifies which core elements, extensions, vocabularies, and value sets SHALL\
+      \ be present in the resource and constrains the way the elements are used when\
+      \ using this profile. It provides the floor for standards development for specific\
+      \ use cases."
+    exampleBoolean: false
+    name: US Core Laboratory Result Observation Profile
   - reference:
       reference: StructureDefinition/us-core-patient
     description: The US Core Patient Profile meets the U.S. Core Data for Interoperability
@@ -81,20 +124,6 @@ definition:
       for standards development for specific use cases.
     exampleBoolean: false
     name: US Core Patient Profile
-  - reference:
-      reference: CapabilityStatement/us-core-server
-    description: This Section describes the expected capabilities of the US Core Server
-      actor which is responsible for providing responses to the queries submitted
-      by the US Core Requestors. The complete list of FHIR profiles, RESTful operations,
-      and search parameters supported by US Core Servers are defined. Systems implementing
-      this capability statement should meet the ONC 2015 Common Clinical Data Set
-      (CCDS) access requirement for Patient Selection 170.315(g)(7) and Application
-      Access - Data Category Request 170.315(g)(8) and the ONC [U.S. Core Data for
-      Interoperability (USCDI) Version 4 July 2023](https://www.healthit.gov/sites/isa/files/2023-07/Final-USCDI-Version-4-July-2023-Final.pdf).  US
-      Core Clients have the option of choosing from this list to access necessary
-      data based on their local use cases and other contextual requirements.
-    exampleBoolean: false
-    name: US Core Server CapabilityStatement
   page:
     nameUrl: toc.html
     title: Table of Contents

input/examples-yaml/condition-encounter-diagnosis-addl-legacycode-example1.yml

@@ -0,0 +1,53 @@
+resourceType: Condition
+id: encounter-diagnosis-example3
+meta:
+  extension:
+  - url: http://hl7.org/fhir/StructureDefinition/instance-name
+    valueString: Encounter Diagnosis Example 1
+  - url: http://hl7.org/fhir/StructureDefinition/instance-description
+    valueMarkdown: This example of a US Core Condition Encounter Diagnosis Profile
+      illustrates its use to capture information about a patient's encounter diagnosis.
+  profile:
+  - http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-encounter-diagnosis
+extension:
+- url: http://hl7.org/fhir/StructureDefinition/condition-assertedDate
+  valueDateTime: 2015-10-31
+clinicalStatus:
+  coding:
+  - system: http://terminology.hl7.org/CodeSystem/condition-clinical
+    code: resolved
+verificationStatus:
+  coding:
+  - system: http://terminology.hl7.org/CodeSystem/condition-ver-status
+    code: confirmed
+category:
+- coding:
+  - system: http://terminology.hl7.org/CodeSystem/condition-category
+    code: encounter-diagnosis
+    display: Encounter Diagnosis
+
+# ============= test codes for QA review =================
+
+code:
+  coding:
+  - system: http://snomed.info/sct
+    code: '39065001'
+    display: Burn of ear
+    version: http://snomed.info/sct/731000124108
+
+  - system: http://example.org/fhir/codes
+    code: FOO
+    display: Foo
+
+  text: Foo
+
+# ============= test codes for QA review =================
+
+subject:
+  reference: Patient/example
+  display: Amy Shaw
+encounter:
+  reference: Encounter/example-1
+onsetDateTime: 2015-10-31
+abatementDateTime: 2015-12-01
+recordedDate: 2015-11-01

input/examples-yaml/condition-encounter-diagnosis-example1.yml

@@ -25,13 +25,19 @@ category:
   - system: http://terminology.hl7.org/CodeSystem/condition-category
     code: encounter-diagnosis
     display: Encounter Diagnosis
+
+# ============= test codes for QA review =================
+
 code:
   coding:
   - system: http://snomed.info/sct
     code: '39065001'
     display: Burn of ear
     version: http://snomed.info/sct/731000124108
   text: Burnt Ear
+
+# ============= test codes for QA review =================
+
 subject:
   reference: Patient/example
   display: Amy Shaw

input/examples-yaml/condition-encounter-diagnosis-legacycode-example1.yml

@@ -0,0 +1,53 @@
+resourceType: Condition
+id: encounter-diagnosis-example2
+meta:
+  extension:
+  - url: http://hl7.org/fhir/StructureDefinition/instance-name
+    valueString: Encounter Diagnosis Example 1
+  - url: http://hl7.org/fhir/StructureDefinition/instance-description
+    valueMarkdown: This example of a US Core Condition Encounter Diagnosis Profile
+      illustrates its use to capture information about a patient's encounter diagnosis.
+  profile:
+  - http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-encounter-diagnosis
+extension:
+- url: http://hl7.org/fhir/StructureDefinition/condition-assertedDate
+  valueDateTime: 2015-10-31
+clinicalStatus:
+  coding:
+  - system: http://terminology.hl7.org/CodeSystem/condition-clinical
+    code: resolved
+verificationStatus:
+  coding:
+  - system: http://terminology.hl7.org/CodeSystem/condition-ver-status
+    code: confirmed
+category:
+- coding:
+  - system: http://terminology.hl7.org/CodeSystem/condition-category
+    code: encounter-diagnosis
+    display: Encounter Diagnosis
+
+# ============= test codes for QA review =================
+
+code:
+  coding:
+  # - system: http://snomed.info/sct
+  #   code: '39065001'
+  #   display: Burn of ear
+  #   version: http://snomed.info/sct/731000124108
+
+  - system: http://example.org/fhir/codes
+    code: FOO
+    display: Foo
+
+  text: Foo
+
+# ============= test codes for QA review =================
+
+subject:
+  reference: Patient/example
+  display: Amy Shaw
+encounter:
+  reference: Encounter/example-1
+onsetDateTime: 2015-10-31
+abatementDateTime: 2015-12-01
+recordedDate: 2015-11-01

input/examples-yaml/condition-encounter-diagnosis-text-only-example1.yml

@@ -0,0 +1,43 @@
+resourceType: Condition
+id: encounter-diagnosis-example4
+meta:
+  extension:
+  - url: http://hl7.org/fhir/StructureDefinition/instance-name
+    valueString: Encounter Diagnosis Example 1
+  - url: http://hl7.org/fhir/StructureDefinition/instance-description
+    valueMarkdown: This example of a US Core Condition Encounter Diagnosis Profile
+      illustrates its use to capture information about a patient's encounter diagnosis.
+  profile:
+  - http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition-encounter-diagnosis
+extension:
+- url: http://hl7.org/fhir/StructureDefinition/condition-assertedDate
+  valueDateTime: 2015-10-31
+clinicalStatus:
+  coding:
+  - system: http://terminology.hl7.org/CodeSystem/condition-clinical
+    code: resolved
+verificationStatus:
+  coding:
+  - system: http://terminology.hl7.org/CodeSystem/condition-ver-status
+    code: confirmed
+category:
+- coding:
+  - system: http://terminology.hl7.org/CodeSystem/condition-category
+    code: encounter-diagnosis
+    display: Encounter Diagnosis
+
+# ============= test codes for QA review =================
+
+code:
+  text: Foo
+
+# ============= test codes for QA review =================
+
+subject:
+  reference: Patient/example
+  display: Amy Shaw
+encounter:
+  reference: Encounter/example-1
+onsetDateTime: 2015-10-31
+abatementDateTime: 2015-12-01
+recordedDate: 2015-11-01