United States Health Information Knowledgebase

 

You are viewing the Abridged Children's EHR Format.
To view the Full Children's EHR Format, you must first agree to the HL7 License Agreement.

MS Excel
Download as an MS Excel spreadsheet.
[Download Excel ReaderExit Disclaimer]
PDF
Download as a PDF file.
[Download PDF ReaderExit Disclaimer]
MS Word
Download as an MS Word document.
[Download Word ReaderExit Disclaimer]

sort Req ID
sort Title
sort Release Package
Release Package(s) Selected
sort Description
sort Topic Area
Topic Area(s) Selected
sort Type
Type(s) Selected
sort Critical/Core
Critical/Core(s) Selected
Req-252Administrative Transaction Processing2013 Format
STATEMENT: Support the creation (including using external data sources, if necessary electronic interchange, and processing of transactions listed below that may be necessary for encounter management during an episode of care.
DESCRIPTION: Support the creation...
STATEMENT: Support the creation (including using external data sources, if necessary electronic interchange, and processing of transactions listed below that may be necessary for encounter management during an episode of care.
DESCRIPTION: Support the creation (including using external data sources, if necessary electronic interchange, and processing of transactions listed below that may be necessary for encounter management during an episode of care.
· The EHR system shall capture the patient health-related information needed for administrative and financial purposes including reimbursement.
· Captures the episode and encounter information to pass to administrative or financial processes (e.g. triggers transmissions of charge transactions as by-product of on-line interaction including order entry, order statusing, result entry, documentation entry, medication administration charting
· Automatically retrieves information needed to verify coverage and medical necessity.
· As a byproduct of care delivery and documentation: captures and presents all patient information needed to support coding. Ideally performs coding based on documentation.
· Clinically automated revenue cycle - examples of reduced denials and error rates in claims.
· Clinical information needed for billing is available on the date of service.
· Physician and clinical teams do not perform additional data entry / tasks exclusively to support administrative or financial processes.
Show Full Text
Registry LinkagesFunctionno
Req-251Health Service Reports at the Conclusion of an Episode of Care2013 Format
STATEMENT: Support the creation of health service reports at the conclusion of an episode of care. Support the creation of health service reports to authorized health entities, for example public health, such as notifiable condition...
STATEMENT: Support the creation of health service reports at the conclusion of an episode of care. Support the creation of health service reports to authorized health entities, for example public health, such as notifiable condition reports, immunization, cancer registry and discharge data that a provider may be required to generate at the conclusion of an episode of care.
DESCRIPTION: Effective use of this function means that providers do not perform additional data entry to support health management programs and reporting.
Show Full Text
Registry LinkagesFunctionno
Req-546Support ability to export data for non-interfaced registries2013 FormatThe system SHALL provide user controlled export features such as protected text or data files for registries that can't or won't accept interfaced or service fed data.Registry LinkagesNormative Statementsno
Req-547Support the tracking of the release of information to outside registries through linkage mechanisms2013 Format
The system SHALL provide data elements that support the tracking of the release of information to outside registries through linkage mechanisms. Release tracking must cascade to the patient level (X patient's data linked to Y...
The system SHALL provide data elements that support the tracking of the release of information to outside registries through linkage mechanisms. Release tracking must cascade to the patient level (X patient's data linked to Y registry. Data elements: Releasing System, Receiving System, Date and Time of Release, Releasing Agent, Reason for Release, Trust Relationship, Release Mechanism.
Show Full Text
Registry LinkagesNormative Statementsno
Req-544Ability to comply with registry sharing/linking regulations and standards2013 FormatThe system SHALL comply with registry sharing/linking regulations and standards (HIPAA, HITECH, CHIPRA, etc.Registry LinkagesNormative Statementsno
Req-545Ability to comply with industry standards for interfaces and services2013 FormatThe system SHALL comply with industry standards for interfaces and services within the limitations of currently accepted standardsRegistry LinkagesNormative Statementsno
Req-677Service reports2013 Format
Lorem, ipsum, dolor, sit, amet, consectetur, adipiscing, elit, Ut, egestas, dolor, nec, ipsum, luctus, non, varius, felis, blandit, Quisque, facilisis, pellentesque, nisi, Sed, rutrum, sodales, nisl, Duis, mattis, ipsum, a, laoreet, pharetra, quam, eros, porta, nisl, eget, pellentesque, augue, purus, eu, nunc
You are viewing the Abridged Children's EHR Format. To view the Full Children's EHR Format, you must first agree to the HL7 License Agreement.
Registry LinkagesNormative Statementsyes
Req-668Automate data retrieval2013 Format
Lorem, ipsum, dolor, sit, amet, consectetur, adipiscing, elit, Ut, egestas, dolor, nec, ipsum, luctus, non, varius, felis, blandit, Quisque, facilisis, pellentesque, nisi, Sed, rutrum, sodales, nisl, Duis, mattis, ipsum, a, laoreet, pharetra, quam, eros, porta, nisl, eget, pellentesque, augue, purus, eu, nunc
You are viewing the Abridged Children's EHR Format. To view the Full Children's EHR Format, you must first agree to the HL7 License Agreement.
Registry LinkagesNormative Statementsno
Req-1053Access & Interoperability2013 FormatAccess and interoperability refers to the ability of school-based systems to provide access to and/or bi-directional sharing of data with external systems in standard formats.School-Based LinkagesFunctionno
Req-1055Access to child's medical records2013 FormatThe system SHALL enable appropriate access to the child's medical record to school-based clinicians.School-Based LinkagesNormative Statementsno
Req-1054FERPA compliance2013 FormatThe system SHALL comply with Family Educational Rights and Privacy Act (FERPA rules.School-Based LinkagesNormative Statementsno
Req-1056Access to school-based health record2013 FormatThe system SHOULD enable appropriate access to the school-based health record for requesting providers and SHALL capture, where necessary, parent/guardian authorization to share data in the record, with adequate specificity as to what information is allowed to be shared, with which caregivers (both clinical and non-clinical and for what purpose.School-Based LinkagesNormative Statementsno
Req-550Support patient consent requirements based on law2013 FormatThe system SHOULD determine the need for minor patient consent based on determination of age of majority based on jurisdictional law.Security and ConfidentialityNormative Statementsno
Req-549Define context for principal authorization2013 FormatThe system MAY provide the ability to define context for the purpose of principal authorization based on identity, role, work assignment, present condition, location, patient consent, or patient's present conditionSecurity and ConfidentialityNormative Statementsno
Req-558Ability to document limitations on the patient's parents' level of authority2013 FormatThe system SHALL provide the ability to document limitations on the patient's parents' level of authority to make decisions on behalf of the patient or access health information about the patient.Security and ConfidentialityNormative Statementsno
Req-559Ability to document parental (guardian) notification or permission2013 FormatThe system SHALL provide the ability to document parental (guardian notification or permission for consenting minors to receive some treatments as required by institutional policy or jurisdictional law.Security and ConfidentialityNormative Statementsno
Req-552Determine need for minor patient consent for outside access to content2013 FormatThe system MAY determine the need for minor patient consent to permit outside access to content based on determination of age of majority within a legal jurisdiction, possibly in combination with record content to be accessed.Security and ConfidentialityNormative Statementsno
Req-573Entity Authorization.2013 Format
STATEMENT: Manage the sets of access-control permissions granted to entities that use an EHR-S (EHR-S Users
Enable EHR-S security administrators to grant authorizations to users, for roles, and within contexts. A combination of these authorization...
STATEMENT: Manage the sets of access-control permissions granted to entities that use an EHR-S (EHR-S Users
Enable EHR-S security administrators to grant authorizations to users, for roles, and within contexts. A combination of these authorization categories may be applied to control access to EHR-S functions or data within an EHR-S, including at the application or the operating system level.

DESCRIPTION: EHR S Users are authorized to use the components of an EHR-S according to their identity, role, work-assignment, location and/or the patient's present condition and the EHR S User's scope of practice within a legal jurisdiction.
- User based authorization refers to the permissions granted or denied based on the identity of an individual. An example of User based authorization is a patient defined denial of access to all or part of a record to a particular party for privacy related reasons. Another user based authorization is for a tele-monitor device or robotic access to an EHR-S for prescribed directions and other input.
- Role based authorization refers to the responsibility or function performed in a particular operation or process. Example roles include: an application or device (tele-monitor or robotic or a nurse, dietician, administrator, legal guardian, and auditor.
- Context-based Authorization is defined by ISO 10181-3 Technical Framework for Access Control Standard as security-relevant properties of the context in which an access request occurs, explicitly time, location, route of access, and quality of authentication. For example, an EHR-S might only allow supervising providers' context authorization to attest to entries proposed by residents under their supervision.
In addition to the ISO standard, context authorization for an EHR-S is extended to satisfy special circumstances such as, work assignment, patient consents and authorizations, or other healthcare-related factors. A context-based example is a patient-granted authorization to a specific third party for a limited period to view specific EHR records.
Another example is a right granted for a limited period to view those, and only those, EHR records connected to a specific topic of investigation.
Show Full Text
Security and ConfidentialityFunctionno
Req-590Document assent for patients unable to consent2013 Format
Lorem, ipsum, dolor, sit, amet, consectetur, adipiscing, elit, Ut, egestas, dolor, nec, ipsum, luctus, non, varius, felis, blandit, Quisque, facilisis, pellentesque, nisi, Sed, rutrum, sodales, nisl, Duis, mattis, ipsum, a, laoreet, pharetra, quam, eros, porta, nisl, eget, pellentesque, augue, purus, eu, nunc
You are viewing the Abridged Children's EHR Format. To view the Full Children's EHR Format, you must first agree to the HL7 License Agreement.
Security and ConfidentialityNormative Statementsno
Req-671Define formal health record2013 Format
Lorem, ipsum, dolor, sit, amet, consectetur, adipiscing, elit, Ut, egestas, dolor, nec, ipsum, luctus, non, varius, felis, blandit, Quisque, facilisis, pellentesque, nisi, Sed, rutrum, sodales, nisl, Duis, mattis, ipsum, a, laoreet, pharetra, quam, eros, porta, nisl, eget, pellentesque, augue, purus, eu, nunc
You are viewing the Abridged Children's EHR Format. To view the Full Children's EHR Format, you must first agree to the HL7 License Agreement.
Security and ConfidentialityNormative Statementsno
Req-665Mask selected EHR data2013 Format
Lorem, ipsum, dolor, sit, amet, consectetur, adipiscing, elit, Ut, egestas, dolor, nec, ipsum, luctus, non, varius, felis, blandit, Quisque, facilisis, pellentesque, nisi, Sed, rutrum, sodales, nisl, Duis, mattis, ipsum, a, laoreet, pharetra, quam, eros, porta, nisl, eget, pellentesque, augue, purus, eu, nunc
You are viewing the Abridged Children's EHR Format. To view the Full Children's EHR Format, you must first agree to the HL7 License Agreement.
Security and ConfidentialityNormative Statementsyes
Req-1244Legal confidentiality requirements for minors2013 FormatThe system SHALL enable users to implement all applicable confidentiality rules regarding health information of minors; note that these rules exist at more than one level, e.g., National and StateSecurity and ConfidentialityNormative Statementsno
Req-1245Multiple and flexible models of consent2013 FormatMultiple and flexible models of consentSecurity and ConfidentialityFunctionno
Req-1246Separate consent, assent and permission2013 FormatThe system SHALL support the recording of consent, assent, and permission as separate artifacts.Security and ConfidentialityNormative Statementsno
Req-1247Emergency consent documentation2013 FormatThe system SHALL record/document the appropriate data associated with emergency consent, i.e., consent when consent from parents or legal guardians cannot be obtained.Security and ConfidentialityNormative Statementsno
Scroll To Top