Type | Standard / Implementation Specification | Standards Process Maturity | Implementation Maturity | Adoption Level | Federally required | Cost | Test Tool Availability |
---|---|---|---|---|---|---|---|
Standard
|
Final
|
Production
|
Feedback Requested |
No
|
Free
|
N/A
|
Limitations, Dependencies, and Preconditions for Consideration |
Applicable Value Set(s) and Starter Set(s)
|
---|---|
|
|
Comment
Submitted by cmcdonald on
Should clarify what is meant…
Should clarify what is meant by a nursing intervention and provide a definition and examples. If a request for vital signs is a nursing intervention then it will be hard to know when the request is fulfilled. if the code doesn't match it will be hard to manage the process from request to fulfillment
Submitted by dvreeman on
We are delighted to see the…
We are delighted to see the addition of Nursing content in the 2017 ISA and concur with all of the recommendations for use of LOINC and SNOMED CT.
Submitted by gldickinson on
Preserving Clinical Context
General Comments:
USCDI specifies lots of clinical data classes and data elements
It is crucial to consider, determine and resolve how clinical content and context are bound together and preserved in USCDI. The ultimate end user (often a clinician) must be able to readily discern context and inter-relationships – otherwise USCDI places an undue (and often unresolvable) burden on this user. Only the source EHR/HIT system can structure clinical content and context properly. Once data is stuffed into the USCDI framework and related exchange artifact (e.g., FHIR resources) this opportunity is forever lost.