Regarding TerminationReason, we do not see a workflow extension reason which is appropriate to our IG. mCODE applies TerminationReason to profiles based on MedicationStatement and Procedure, which are not listed as contexts in the closest matching workflow extensions workflow-reasonCode and workflow-reasonReference. The data-absent-reason standard extension was also not suitable for our purposes because it is bound to the http://hl7.org/fhir/ValueSet/data-absent-reason with a required binding strength and mCODE needed a term which specifically identifies ineffective treatment as a reason. We could further work with HL7 to change the binding strength of the data-absent-reason value set to extensible at some point in the future but for our purposes at this time, we need to keep our existing value set. Proposed Resolution: Considered for future use