Representing Patient Address
Patient Preference/Consent
FormGuide

Help

1. Optional: Background Text / Cover Letter

The "Optional Background Text / Cover Letter" field provides space for additional context or introductory information related to your comment.

This field is entirely optional and serves the following purposes:

  • Provides context for reviewers
  • Serves as an introduction if submitting multiple comments
  • Functions as a cover letter for formal submissions

If you are submitting a single comment for a specific data class or element, you may leave this field blank. For multiple comments, this space is useful for explaining the overall purpose or connection between your comments.
 

Optional Background Text / Cover Letter

Fig 1 The "Optional Background Text / Cover Letter" field allows users to provide contextual information or introductory remarks for their comment submission.

 2. Complete the Comment Form

The comment form contains several fields that require your input:

ISA Content: This field is automatically populated based on the page you are currently viewing. No action is required.

Standards and Implementation Specifications: This drop-down menu is pre-selected based on the topic you're commenting on. The selection reflects the relevant standard or implementation specification for your current page.

Subject: Enter a concise title that summarizes the focus of your comment. This helps reviewers quickly understand the nature of your feedback.

Comment: This is the main field where you provide your detailed feedback, concerns, or suggestions. The comment box includes a text editor with formatting options that allow you to:

  • Format text as bold or italic
  • Insert hyperlinks
  • Create bullet points
  • Create numbered lists
  • Apply strike-through formatting
  • Attach images
  • Insert tables

Use these formatting options as needed to clearly present your information.

text editor toolbar

Fig 2 The comment text editor toolbar provides formatting options including bold, italic, links, lists, tables, and image insertion capabilities.

3. Optional: Add Additional Comments

If you need to provide feedback on multiple aspects of the ISA content, you can add additional comments:

  1. After completing your first comment, locate and click the link labeled "Comment on another interoperability need" at the bottom of the form.
  2. A new comment section will appear, allowing you to enter details for your additional comment.
  3. For this new comment section, the "ISA Content" and "Standards and Implementation Specifications" fields will not be automatically populated. You must select the appropriate content and specification from the drop-down menus for each additional comment.
  4. Complete all required fields for your additional comment.
  5. Repeat this process for each additional comment you wish to submit.
Comment on another interoperability need

Fig 3 The "Comment on another interoperability need" link enables users to add multiple comments within a single submission.

4. Optional: Upload Supporting Files

The platform allows you to upload supporting documentation to enhance your comment:

  1. Locate the "File Upload" section at the bottom of the comment form.
  2. Click to upload any files (such as PDFs or documents) that provide additional context, evidence, or clarification for your comment.

Important: If you have already entered your comments using the form fields, there is no need to upload duplicate content in PDF format. The file upload feature is intended for supplementary materials only. Please avoid uploading files that contain the same information already provided in your comment text.

File Upload

Fig 4 The "File Upload" section permits users to attach supporting documentation that supplements their written comments.

5. Optional: Save and Exit

If you need to pause your work and return to complete your comment later:

  1. Click the "Save and Exit" button at the bottom of the form.
  2. Your comment will be saved as a draft that you can access and complete later.
  3. When you return to the platform, you will see a red triangle with an exclamation mark next to the "Return to saved Comment" button, indicating that you have saved comments in draft status.
  4. Click the "Return to saved Comment " button to continue working on your draft.
  5. You will be taken to a review page where you can:
    1. Select "Submit Comment" to officially submit your feedback.
    2. Click "Edit" to return to the comment form and make changes
    3. Select "Discard Draft" to delete the saved draft and start fresh
Return to saved Comment

Fig 5 A red triangle with exclamation mark indicator appears next to the "Return to saved Comment" button when draft comments are saved in the system.

6. Review and Submit

Once you have completed your comment:

  1. Click the "Review and Submit" button at the bottom of the form.
  2. This will take you to a review screen displaying your comment(s) in full.
  3. Review all information for accuracy and completeness.
  4. On this review screen, you have three options:
    1. Click "Submit Comment" to officially submit your feedback
    2. Click "Edit" to return to the comment form and make changes
    3. Click "Discard Draft" to delete the comment and start fresh
  5. The review screen also includes a "Print" button that allows you to create a printed copy of your comments for your records.
  6. If you choose to submit, your comment will be recorded in the system and made available for review by the appropriate stakeholders.
Review and Submit

Fig 6 The review screen includes a "Print" button that allows users to create a record of their comment submission.

ISA Comments

Close

Add a New Comment

Review comment and Submit

Edit
Comment #1

Comment

Submitted by Cole Downs on

Patient Name Requirements

I support AHIMA’s Patient Naming Policy to improve patient safety as well as decreasing the financial burden of duplicate tests that are ordered when patient records cannot be assimilated.

Submitted by Amanda Rodriguez on

AHIMA Patient Naming Policy

I support AHIMA's Patient Naming Policy to improve patient safety, reduce the risk of patient identity errors, efficiently share health data across systems, and reduce the costs associated with patient identity errors. 

Submitted by mceraso on

Patient Naming Policy

I support AHIMA’s Patient Naming Policy to improve patient safety. 

Submitted by Djordjevic on

Patient Naming Policy

I support AHIMA’s Patient Naming Policy to decrease the financial burden of duplicate tests that are ordered when patient records cannot be assimilated.

Submitted by tmulvenn1 on

Patient Name Requirements

I support adopting the AHIMA Recommended Data Elements for capturing the legal name to improve patient safety, reduce overlays, and ensure interoperability.

Submitted by CTurrietta on

Patient Naming Policy

I support AHIMA’s Patient Naming Policy in support of patient safety. Duplicates, overlaps, and overlays not only create a financial burden due to duplicate tests but can also lead to errors that jeopardize the health and safety of patients. The data elements recommended by AHIMA support consistency and quality data. A patient naming policy with these legal name requirements and quality principles protects everyone.

Submitted by Katherine Lusk on

Capture of Name

I support the adoption of the AHIMA Recommended data elements for capture of individuals names.  Consistent use of the legal name and the AHIMA conventions will improve patient safety and interoperability.  

Submitted by Katherine Lusk on

Capture of Patient Names

I support the adoption of the AHIMA recommended data elements for capture in the master patient index as a level playing field for all participants in the healthcare ecosystem.  The AHIMA policy contains practical guidance for the community including capture of naming conventions for multiple births, in-vitro care diagnosing and care delivery and individuals with one name.  The policy can support the capture of individual's names as a patient, insured individual, or clinician receiving a direct secure messaging.  The type of standardization via a national policy has broad ranging positive impacts for patient safety and for efficiencies. 

Submitted by Beth Juliano on

Patient Name Requirements

I support the adoption of the AHIMA Recommended Data Elements for Capture in the Master Patient Index, specifically use of legal name.  Consistent use of legal name would improve patient safety and interoperability.