Non-Patient File Sharing (NPFS) defines how to enable sharing of non-patient files such as clinical workflow definitions, domain policies, and stylesheets. Those files can be created and consumed by many different systems involved in a wide variety of data sharing workflows.
Section NumberIdentify the most specific section number the issue occurs (e.g. 4.1.2)
2:3.87.4.4.2
IssueDescribe your issue. Don't write a book, but do include enough to indicate what you see as a problem.
There is some strange indenting when describing the failure cases:
Proposed ChangePropose a resolution to your issue (e.g., suggested new wording or description of a way to address the issue). The committee might simply accept your suggested text. Even if they don't, it gives a good sense of what you are looking for. Leaving this blank means you can't imagine how to resolve the issue, which makes it easier for the committee to admit they can't imagine how to resolve it either and leave it unresolved.
I think these do not need to be indented.
Priority:
Low: Typo or other minor classification that an editor can manage. Requires no group discussion.
Section Number Identify the most specific section number the issue occurs (e.g. 4.1.2) 2:3.87.4.4.2 Issue Describe your issue. Don't write a book, but do include enough to indicate what you see as a problem. There is some strange indenting when describing the failure cases:
Proposed Change Propose a resolution to your issue (e.g., suggested new wording or description of a way to address the issue). The committee might simply accept your suggested text. Even if they don't, it gives a good sense of what you are looking for. Leaving this blank means you can't imagine how to resolve the issue, which makes it easier for the committee to admit they can't imagine how to resolve it either and leave it unresolved.
I think these do not need to be indented.
Priority: