Comments on the ISA are accepted year-round, and changes are made to the web version of the ISA frequently throughout the year, based on comments and other changes to the health IT standards environment as ONC becomes aware of them. An annual Review and Comment period also occurs each summer-fall, when a majority of comments are received. See the process timeline below for more details.
Annual ISA Process Timeline
- January: Current Year Reference Edition is published, web version of ISA is available for ongoing review and comments.
- Winter/Spring/Summer: Changes may be made to the web-version of the ISA throughout the year, while the ISA Reference Edition remains static.
- Late Summer/Early Fall: Annual Review and Comment Period opens for sixty days - site changes are on hold so all reviewers are seeing the same content.
- Fall: ONC and HHS staff review comments received, make site updates and prepare the following year's Reference Edition for publication by early January.
How to Comment on the ISA
- An ISA site account is required in order to comment on the ISA.
- If you have an account already, click the "Login" button at the top right of the ISA.
- To create an account, click the "Login" button, then "Create new account" tab above the login window. Account approval is required, and is generally completed within 1 - 24 hours.
- Once you're authenticated to the ISA site, you can submit comments on most ISA pages - just scroll to the bottom of the relevant page, enter the text of your comment (or provide attachments, if needed) and submit. Your comment will be reviewed by ONC or other HHS subject matter experts, and changes will be considered for publication to the ISA.
- While comments by topic (posted to individual Interoperability Need pages) are preferred, and allow greater visibility to your comments by other industry stakeholders, consolidated comment letters are also accepted. You may provide these comments on general information pages, and ONC staff will triage them, and assign them to subject matter experts.
Comment
Submitted by Ralph O'Connor on
Sharing race/ethnicity data between systems
Is there a requirement that race/ethnicity be shared along with other medical information?
The clinic where I volunteer has an EHR interface with the state's immunization registry that seems to only upload data on the immunization but race/ethnicity have to be entered manually. Is this not an interoperability requirement?
I have also volunteered with our local health department's COVID-19 data quality team for almost two years. Most of the Electronic Health Records for positive COVID-19 PCR tests that labs send to the state's online notifiable disease system do not include race and ethnicity. In addition, about 10 % of the ELRs don't have a valid phone number (no phone or area code repeated etc.) and about 5 % do not have a valid residential address for the person (no address or the address of the testing facility etc.). Is there a way to fix this on the front end? We spend most of our time tracking down this missing data. Thanks.
Submitted by mxenakis@virtua.org on
Patient Naming Policy
I support AHIMA's Patient Naming Policy to improve patient safety.
Submitted by mbkurilo@immre… on
AIRA Comments
On behalf of the American Immunization Registry Association (AIRA) we are pleased to submit comments on the Office of the National Coordinator’s (ONC’s) updated Interoperability Standards Advisory. These comments are a compilation of the input of our members which include over 80 organizations representing Public Health Immunization Information Systems (IIS), IIS implementers and vendors, non-profit organizations and partners. Immunization Information Systems interface with a broad range of stakeholders, including providers, pharmacists, schools, child care facilities, health plans and payers, among others.
Most of AIRA's comments were uploaded on specific pages, but the comment below likely needs a new page:
AIRA proposes the addition of a new HL7-balloted Implementation guide for Immunization Decision Support Forecast (http://hl7.org/fhir/us/immds/). This emerging FHIR R4 standard has been balloted through HL7, published, and is in use in several pilots and/or proof of concepts. AIRA is happy to discuss in greater detail how to represent this new standard on the ISA. We believe this should fit nicely within Content/Structure or Services/Exchange Standards within their respective Clinical Decision Support sections.
Thank you for the opportunity to provide comments, and please let us know if there are any follow up questions.
Submitted by Bernadette Nunley on
Compassion & Choices Comment USCDIv3
Compassion & Choices provides the attached feedback on the Draft Core Data for Interoperability.
Compassion & Choices Interoperability Standards Comment-9.30.21.pdf
Submitted by Kelly Gwynn on
DirectTrust's Comments on ISA
Thank you for the opportunity to comment on the Interoperability Standards Advisory. See attached.
Submitted by bgradl@eatright.org on
Academy of Nutrition and Dietetics Comments on 2021 ISA
On behalf of the Academy of Nutrition and Dietetics, thank you for the opportunity to provide our feedback on the Interoperability Standards Advisory.
Academy Comments on 2021 Interoperability Standards Advisory.pdf
Submitted by toniki on
terminologies referenced by ISA
It would be very useful to have an "index," so to speak, of all the terminologies/code sets/vocabularies referenced by ISA and where in ISA they're referenced. Does such a thing already exist?
Submitted by College_of_Ame… on
Submitted by Emily Turek on
American Association of Colleges of Nursing submits comments
Please see attached PDF
Submitted by MeganBoyd_Invitae on
Support including Genomics in USCDI v4
Invitae comments in support of elevating the Genomics Data Class to Level 2 and including in USCDI v4. Please find our comments attached.
Invitae_USCDIv4_Sept2022.pdf