Update as follows (not based on any US Core profile): QI-Core Profile-based path Action Include in QI-Core 6.0? Justification QICoreCommunication. implicitRules Keep YES basic content QICoreCommunication. modifierExtension Keep YES basic content QICoreCommunication. status Keep YES Maintain required binding to NonNegativeEventStatus QICoreCommunication. statusReason REMOVE NO This element is not used in a disjoint Communication that is distinct from CommunicationNotDone. Specifically, it has a preferred binding to CommunicationNotDoneReason QICoreCommunication. category REMOVE NO May be useful to indicate the kind of communication desired, but not necessarily needed for the use case. It has a preferred binding to CommunicationCategory (alert, notification, reminder, instruction) QICoreCommunication. medium REMOVE NO May be useful to indicate how communication happens but only example binding to ParticipationMode (e.g., physical presence, online written, email, handwritten, etc.) QICoreCommunication. subject KEEP YES Subject references QICorePatient, Group QICoreCommunication. topic KEEP YES “description of the purpose/content” – preferred binding to CommunicationTopic (e.g., prescription-refill-request, progress-update, report-labs, appointment-reminder, phone-consult, summary-report) QICoreCommunication. encounter REMOVE NO Created as part of encounter – no specific use case for eCQMS QICoreCommunication. sent Keep YES dateTime QICoreCommunication. received Keep YES dateTime QICoreCommunication. recipient Keep YES Reference QICoreDevice, USCoreImplantableDevice, QICoreOrganization, QICorePatient, QICorePractitioner, QICoreRelatedPerson, Group QICoreCommunication. sender Keep YES Reference QICoreDevice, USCoreImplantableDevice, QICoreOrganization, QICorePatient, QICorePractitioner, QICoreRelatedPerson QICoreCommunication. basedOn DO NOT ADD NO No direct use case QICoreCommunication. inResponseTo Do Not Add NO Considered due to QDM to QI-Core mapping. Not in use or clear use case for measures. Meaning is “as reply to” QICoreCommunication. reasonCode Do Not Add NO Considered due to QDM to QI-Core mapping. Starting with QI-Core 5.0.1 Communication.topic should have been added in the mapping but the change happened too late to make that adjustment in the mapping table. Topic is more appropriate to the use case – “description of the purpose/content”.