block vote 2

HL7 · Sep 3, 2024 · b19f48c · b19f48c
1 parent 11226d8
commit b19f48c
Show file tree

Hide file tree

Showing 7 changed files with 12 additions and 24 deletions.
diff --git a/input/fsh/SD_Extensions.fsh b/input/fsh/SD_Extensions.fsh
@@ -113,7 +113,7 @@ Description: "The purpose of a treatment, medication, or procedure."
 Extension: NormalizationBasis
 Id: mcode-normalization-basis
 Title:  "Normalization Basis Extension"
-Description: "How the drug dosage was normalized."
+Description: "The method (e.g., body weight, body surface area, flat dose, age) used to normalize the medication dosage."
 * insert ExtensionContext(DomainResource)
 * insert ExtensionContext(Extension)
 * insert ExtensionContext(MedicationRequest)

diff --git a/input/fsh/SD_Surgery.fsh b/input/fsh/SD_Surgery.fsh
@@ -2,7 +2,7 @@ Profile:  CancerRelatedSurgicalProcedure
 Parent:   USCoreProcedure
 Id: mcode-cancer-related-surgical-procedure
 Title:    "Cancer-Related Surgical Procedure Profile"
-Description: "A surgical action addressing a cancer condition. The scope of this profile has been narrowed to cancer-related procedures by constraining the reasonReference and reasonCode to cancer conditions, one of which is required."
+Description: "A surgical action addressing a cancer condition. The scope of this profile has been narrowed to cancer-related procedures by constraining the reasonReference and reasonCode to cancer conditions, one of which is required. If a procedure occurs that is NOT a surgical procedure, use the US Core Procedure profile."
 * ^extension[FMM].valueInteger = 3
 * subject ^definition = "The patient on whom the procedure was performed"
 * obeys mcode-reason-required

diff --git a/input/fsh/VS_CancerCondition.fsh b/input/fsh/VS_CancerCondition.fsh
@@ -304,9 +304,9 @@ Description: "Codes representing the structure, arrangement, and behavioral char
 * insert SNOMEDCopyrightForVS
 * ^extension[FMM].valueInteger = 4
 * include codes from system ICDO3
-* include codes from system SCT where concept is-a #367651003 "Malignant neoplasm of primary, secondary, or uncertain origin (morphologic abnormality)"
-* include codes from system SCT where concept is-a #399919001 "Carcinoma in situ - category (morphologic abnormality)"
-* include codes from system SCT where concept is-a #399983006 "In situ adenomatous neoplasm - category (morphologic abnormality)"
+* include codes from system SCT where concept is-a #1240414004 "Malignant neoplasm (morphologic abnormality)"
+* include codes from system SCT where concept is-a #1187138006 "Carcinoma in situ (morphologic abnormality)"
+* include codes from system SCT where concept is-a #60286009 "Adenocarcinoma in situ in adenomatous polyp (morphologic abnormality))"
 * SCT#399878004 "Malignant neoplasm with pilar differentiation (morphologic abnormality)"
 * SCT#253035009 "In situ melanocytic morphology (morphologic abnormality)"
 * exclude codes from system SCT where concept is-a #450893003 "Papillary neoplasm, pancreatobiliary-type, with high grade intraepithelial neoplasia (morphologic abnormality)"

diff --git a/input/fsh/VS_Other.fsh b/input/fsh/VS_Other.fsh
@@ -19,36 +19,24 @@ Description:  "How patient's given disease, condition, or ability is trending."
 * SCT#271299001 "Patient's condition worsened (finding)"
 * SCT#709137006 "Patient condition undetermined (finding)"
 
-//only include the following in the Max VS
-//* SCT#103338009 "In full remission (qualifier value)"
-//* SCT#103337004 "In partial remission (qualifier value)"
-/* Added based on FHIR-40811 */
-//* SCT#399409002 "Distant metastasis present (finding)" 
-
 ValueSet:   ConditionStatusTrendMaxVS
 Id: mcode-condition-status-trend-max-vs
 Title: "Condition Status Trend Maximum Value Set"
 Description:  "Like the ConditionStatusTrendVS, but includes two additional deprecated codes. Codes from the SNOMED CT disorder hierarchy were less than ideal because the value of an Observation should be either a finding or a qualifier (see https://confluence.ihtsdotools.org/display/FHIR/Observation+binding for details)."
 * include codes from valueset ConditionStatusTrendVS
 * SCT#550991000124107 "Malignant neoplasm in full remission (disorder)" // FHIR-32837 - MLT_note: SCT FN is displayed. The initial term of "cancer in complete remission" is a synonym for the concept.
-* SCT#551001000124108 "Malignant neoplasm in partial remission (disorder)" // FHIR-32837 - MLT_note: SCT FN is displayed. The initial term of "cancer in partial remission" is a synonym for the concept.
-
-* insert SNOMEDCopyrightForVS
-* ^extension[FMM].valueInteger = 3
+* SCT#551001000124108 "Malignant neoplasm in partial remission (disorder)" // FHIR-32837 - MLT_note: SCT FN is displayed. The initial term of "cancer in partial remission" is a synonym for the concept. 
 // * SCT#281900007 "No abnormality detected (finding)" // better than SCT#260415000 "Not detected (qualifier)" - FHIR-32837
 * SCT#268910001 "Patient's condition improved (finding)"
 * SCT#359746009 "Patient's condition stable (finding)"
 * SCT#271299001 "Patient's condition worsened (finding)"
 * SCT#709137006 "Patient condition undetermined (finding)"
-/*
-   Retired these, replaced with qualifier values
-* SCT#550991000124107 "Malignant neoplasm in full remission (disorder)" // FHIR-32837 - MLT_note: SCT FN is displayed. The initial term of "cancer in complete remission" is a synonym for the concept.
-* SCT#551001000124108 "Malignant neoplasm in partial remission (disorder)" // FHIR-32837 - MLT_note: SCT FN is displayed. The initial term of "cancer in partial remission" is a synonym for the concept.
-*/
 * SCT#103338009 "In full remission (qualifier value)"
 * SCT#103337004 "In partial remission (qualifier value)"
-/* Added based on FHIR-40811 */
 * SCT#399409002 "Distant metastasis present (finding)"
+* insert SNOMEDCopyrightForVS
+* ^extension[FMM].valueInteger = 3
+
 
 ValueSet: CancerDiseaseStatusEvidenceTypeVS
 Id: mcode-cancer-disease-status-evidence-type-vs

diff --git a/input/pagecontent/conformance-profiles.md b/input/pagecontent/conformance-profiles.md
@@ -1,6 +1,6 @@
 ### Profile Base
 
-Most mCODE profiles are based on US Core profiles defined in the [US Core Implementation Guide (v4.0.1)](http://hl7.org/fhir/us/core/index.html). For example, [CancerPatient] is based on the [US Core Patient][USCorePatient] profile. Because of the way profiles work in FHIR, any resource that validates against an mCODE profile that is based a US Core profile will automatically be in compliance with the US Core profile.
+Most mCODE profiles are based on US Core profiles defined in the [US Core Implementation Guide (v6.1.0)](http://hl7.org/fhir/us/core/index.html). For example, [CancerPatient] is based on the [US Core Patient][USCorePatient] profile. Because of the way profiles work in FHIR, any resource that validates against an mCODE profile that is based a US Core profile will automatically be in compliance with the US Core profile.
 
 Where US Core does not provide an appropriate base profile, mCODE profiles FHIR resources. An example is [CancerDiseaseStatus], based on Observation because US Core does not provide a profile for non-laboratory observations.
 

diff --git a/input/pagecontent/index.md b/input/pagecontent/index.md
@@ -26,7 +26,7 @@ The overall scope of mCODE and the relationships between mCODE profiles is shown
 
 1. mCODE does not define a specific set of information that must be collected for each cancer patient. Instead, mCODE presents a set of patterns or templates, including controlled terminologies, to be used when certain data in the above groups are shared. ***Example:** mCODE includes a FHIR profile for ECOG performance status, but not every cancer patient undergoes such an evaluation. However, if a patient DOES have an ECOG performance evaluation, that information must conform to mCODE's ECOG profile when shared.*
 
-2. If mCODE does not have a profile for a certain type of data, that data still can be included with mCODE data using an appropriate resource or profile. The lack of an mCODE profile only means that mCODE does not impose requirements above and beyond the base FHIR specifications or US Core. ***Example:** mCODE does not include a profile for care teams. However, users can share care team information using [FHIR's CareTeam resource](https://hl7.org/fhir/R4B/careteam.html), using a profile such as [US Core CareTeam](http://hl7.org/fhir/us/core/STU5.0.1/StructureDefinition-us-core-careteam.html).*
+2. If mCODE does not have a profile for a certain type of data, that data still can be included with mCODE data using an appropriate resource or profile. The lack of an mCODE profile only means that mCODE does not impose requirements above and beyond the base FHIR specifications or US Core. ***Example:** mCODE does not include a profile for care teams. However, users can share care team information using [FHIR's CareTeam resource](https://hl7.org/fhir/R4B/careteam.html), using a profile such as [US Core CareTeam](http://hl7.org/fhir/us/core/STU6.1.0/StructureDefinition-us-core-careteam.html).*
 
 3. Additional profiles can be derived from mCODE profiles. It is expected that mCODE will serve as the basis for future implementation guides dealing with new use cases, particular types of cancer, or specific demographic groups using mCODE as a base. ***Example:** Radiation oncologists and vendors collaborated on a [radiation therapy implementation guide](http://hl7.org/fhir/us/codex-radiation-therapy/STU1/) that extends mCODE and facilitates structured data sharing between radiation oncology information systems and other health information systems.*
 

diff --git a/sushi-config.yaml b/sushi-config.yaml
@@ -13,7 +13,7 @@ description: mCODE™ (short for Minimal Common Oncology Data Elements) is an in
 license: CC0-1.0
 fhirVersion: 4.0.1
 dependencies:
-  hl7.fhir.us.core: 5.0.1
+  hl7.fhir.us.core: 6.1.0
   hl7.fhir.uv.genomics-reporting: 2.0.0
   hl7.fhir.uv.extensions: 5.1.0-cibuild
 extension: