NOTE 1 TO BALLOT COMMENTERS: To the extent possible, QI-Core derives content from US Core profiles and extensions. There are a number of QI-Core profiles inherited directly from US Core profiles (i.e. US Core Implantable Device Profile, FHIR Vital Signs, US Core Smoking Status etc.) We seek implementer feedback regarding other FHIR implementation guides appropriate to directly reference including recommendations for the most appropriate method to address them, for example, minimal Common Ontology Data Elements (mCode) , CARIN Consumer Directed Payer Data Exchange (CARIN IG for Blue Button) , and other suggestions.   NOTE 2 TO BALLOT COMMENTERS: QI-Core has developed specific profiles based on existing US Core profiles adding constraints and/or additional must support elements required for the quality measurement and clinical decision support use cases. Such profiles in QI-Core 6.0 include: QICore Observation Clinical Result QICore Laboratory Result Observation QICore Observation Screening Assessment  QICore Simple Observation Please provide input regarding the value of developing similar QI-Core profiles based on the following existing US Core 6.1.0 profiles. Such changes could include provision of more specific value set bindings or further constraints on cardinality and addition of must support items: US Core Smoking Status Observation Profile   US Core Observation Sexual Orientation Profile US Core Observation Occupation Profile US Core Observation Pregnancy Intent Profile US Core Observation Pregnancy Status Profile   NOTE 3 TO BALLOT COMMENTERS: Changes in QI-Core STU 6.0 scope include a simplification to reduce the number of must support elements and further constraints on US Core content. The approach in previous QI-Core versions listed as key elements all metadata that might be relevant to clinical quality measurement and clinical decision support use cases. QI-Core STU 6.0 advances the concept that measurement and decision support real-world use cases should drive content for the IG. Thus, the profile key element tables are more concise, including only those elements necessary due to the base resource or relevant US Core profile and those elements used by tested and implemented use cases.   Add hyperlink to https://build.fhir.org/ig/FHIR/ig-guidance/readingIgs.html#model-views   describes what is in the Key Elements tab