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.

Results 1-41 of 41
remove Filtering Topic Area on Registry Linkages
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]
Remove All Filters

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-103Care Management2013 Format
Care Management functions are those directly used by providers as they deliver patient care and create an electronic health record. The Record Management (Req-106 functions address the mechanics of creating a...
Care Management functions are those directly used by providers as they deliver patient care and create an electronic health record. The Record Management (Req-106 functions address the mechanics of creating a health record and concepts such as a single logical health record, managing patient demographics, and managing externally generated (including patient originated health data. Thereafter, The additional Care Management functions follow a fairly typical flow of patient care activities and corresponding data, starting with managing the patient history and progressing through consents, assessments, care plans, orders, results etc.

Integral to these care management activities is an underlying system foundation that maintains the privacy, security, and integrity of the captured health information - the information infrastructure of the EHR-S. Throughout the DC functions, conformance criteria formalize the relationships to Information Infrastructure functions. Criteria that apply to all Care Management functions are listed in this header (see Conformance Clause page six for discussion of "inherited" conformance criteria

In the Direct Care functions there are times when actions/activities related to "patients" are also applicable to the patient representative. Therefore, in this section, the term "patient" could refer to the patient and/or the patient's personal representative (e.g. guardian, surrogate
Show Full Text
Activity Clearance, Birth Information, Child Abuse Reporting, Child Welfare, Children with Special Healthcare Needs, EPSDT, Genetic information, Growth Data, Immunizations,...
Activity Clearance, Birth Information, Child Abuse Reporting, Child Welfare, Children with Special Healthcare Needs, EPSDT, Genetic information, Growth Data, Immunizations, Medication Management, Newborn Screening, Parents and Guardians and Family Relationship Data, Patient Identifier, Patient Portals - PHR, Prenatal Screening, Primary Care Management, Quality Measures, Registry Linkages, Security and Confidentiality, Special Terminology and Information, Specialized Scales/Scoring, Well Child/Preventive Care
Show Full Text
Headerno
Req-107Standards Based Interoperability2013 Format
Provide automated health care delivery processes and seamless exchange of clinical, administrative, and financial information through standards-based solutions.
Interoperability standards enable an EHR-S to operate as a set of applications. This results in a unified...
Provide automated health care delivery processes and seamless exchange of clinical, administrative, and financial information through standards-based solutions.
Interoperability standards enable an EHR-S to operate as a set of applications. This results in a unified view of the system where the reality is that several disparate systems may be coming together.
Interoperability standards also enable the sharing of information between EHR systems, including the participation in regional, national, or international information exchanges.
Timely and efficient access to information and capture of information is promoted with minimal impact to the user.
Show Full Text
Immunizations, Prenatal Screening, Registry Linkages, School-Based LinkagesHeaderno
Req-249Health Record Output2013 Format
STATEMENT: Support the definition of the formal health record, a partial record for referral purposes, or sets of records for other necessary disclosure purposes.
DESCRIPTION: Provide hardcopy and electronic output that fully chronicles the healthcare...
STATEMENT: Support the definition of the formal health record, a partial record for referral purposes, or sets of records for other necessary disclosure purposes.
DESCRIPTION: Provide hardcopy and electronic output that fully chronicles the healthcare process, supports selection of specific sections of the health record, and allows healthcare organizations to define the report and/or documents that will comprise the formal health record for disclosure purposes. A mechanism should be provided for both chronological and specified record element output. This may include defined reporting groups (i.e. print sets For example: Print Set A = Patient Demographics, History & Physical, Consultation Reports, and Discharge Summaries. Print Set B = all information created by one caregiver. Print Set C = all information from a specified encounter. An auditable record of these requests and associated exports may be maintained by the system. This record could be implemented in any way that would allow the who, what, why and when of a request and export to be recoverable for review. The system has the capability of providing a report or accounting of disclosures by patient that meets in accordance with scope of practice, organizational policy and jurisdictional law.
Show Full Text
Immunizations, Patient Identifier, Registry Linkages, Security and Confidentiality, Well Child/Preventive CareFunctionno
Req-250Report Generation2013 Format
STATEMENT: Support the export of data or access to data necessary for report generation and ad hoc analysis.
DESCRIPTION: Providers and administrators need access to data in the EHR-S for the generation of both standard...
STATEMENT: Support the export of data or access to data necessary for report generation and ad hoc analysis.
DESCRIPTION: Providers and administrators need access to data in the EHR-S for the generation of both standard and ad hoc reports. These reports may be needed for clinical, administrative, and financial decision-making, as well as for patient use. Reports may be based on structured data and/or unstructured text from the patient's health record.
Show Full Text
Activity Clearance, Birth Information, EPSDT, Immunizations, Patient Identifier, Registry Linkages, Security and Confidentiality, Well Child/Preventive CareHeaderno
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-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-253Manage Allergy, Intolerance and Adverse Reaction List2013 Format
STATEMENT: Create and maintain patient-specific allergy, intolerance and adverse reaction lists.
DESCRIPTION: Allergens, including immunizations, and substances are identified and coded (whenever possible and the list is captured and maintained over time. All pertinent dates,...
STATEMENT: Create and maintain patient-specific allergy, intolerance and adverse reaction lists.
DESCRIPTION: Allergens, including immunizations, and substances are identified and coded (whenever possible and the list is captured and maintained over time. All pertinent dates, including patient-reported events, are stored and the description of the patient allergy and adverse reaction is modifiable over time. The entire allergy history, including reaction, for any allergen is viewable. The list(s includes all reactions including those that are classifiable as a true allergy, intolerance, side effect or other adverse reaction to drug, dietary or environmental triggers. Notations indicating whether item is patient reported and/or provider verified are maintained.
Show Full Text
Child Welfare, Immunizations, Medication Management, Parents and Guardians and Family Relationship Data, Registry Linkages, Well Child/Preventive CareFunctionno
Req-254Manage Assessments2013 Format
STATEMENT: Create and maintain assessments.
DESCRIPTION: During an encounter with a patient, the provider will conduct an assessment that is germane to the age, gender, developmental or functional state, medical and behavioral condition of the...
STATEMENT: Create and maintain assessments.
DESCRIPTION: During an encounter with a patient, the provider will conduct an assessment that is germane to the age, gender, developmental or functional state, medical and behavioral condition of the patient, such as growth charts, developmental profiles, and disease specific assessments. Wherever possible, this assessment should follow industry standard protocols although, for example, an assessment for an infant will have different content than one for an elderly patient. When a specific standard assessment does not exist, a unique assessment can be created, using the format and data elements of similar standard assessments whenever possible.
Show Full Text
Child Abuse Reporting, Child Welfare, Children with Special Healthcare Needs, EPSDT, Parents and Guardians and Family Relationship Data, Primary Care...
Child Abuse Reporting, Child Welfare, Children with Special Healthcare Needs, EPSDT, Parents and Guardians and Family Relationship Data, Primary Care Management, Registry Linkages, Special Terminology and Information, Well Child/Preventive Care
Show Full Text
Functionno
Req-257Manage Immunization Administration2013 Format
STATEMENT: Capture and maintain discrete data concerning immunizations given to a patient including date administered, type, manufacturer, lot number, and any allergic or adverse reactions. Facilitate the interaction with an immunization registry to allow maintenance...
STATEMENT: Capture and maintain discrete data concerning immunizations given to a patient including date administered, type, manufacturer, lot number, and any allergic or adverse reactions. Facilitate the interaction with an immunization registry to allow maintenance of a patient's immunization history.
DESCRIPTION: During an encounter, recommendations based on accepted immunization schedules are presented to the provider. Allergen and adverse reaction histories are checked prior to giving the immunization. If an immunization is administered, discrete data elements associated with the immunization including date, type, manufacturer and lot number are recorded. Any new adverse or allergic reactions are noted. If required, a report is made to the public health immunization registry.
Show Full Text
Activity Clearance, EPSDT, Immunizations, Registry LinkagesFunctionno
Req-273Support for Medication and Immunization Administration2013 Format
STATEMENT: Alert providers to potential administration errors (such as wrong patient, wrong drug, wrong dose, wrong route and wrong time in support of safe and accurate medication administration and support medication administration workflow.
DESCRIPTION: To...
STATEMENT: Alert providers to potential administration errors (such as wrong patient, wrong drug, wrong dose, wrong route and wrong time in support of safe and accurate medication administration and support medication administration workflow.
DESCRIPTION: To reduce medication errors at the time of administration of a medication, the patient is positively identified; checks on the drug, the dose, the route and the time are facilitated. Documentation is a by-product of this checking; administration details and additional patient information, such as injection site, vital signs, and pain assessments, are captured.
Access to drug monograph information may be provided to allow providers to check details about a drug and enhance patient education. Workflow for medication administration is supported through prompts and reminders regarding the "window" for timely administration of medications.
Show Full Text
Immunizations, Medication Management, Registry LinkagesFunctionno
Req-277Registry Notification2013 Format
STATEMENT: Enable the automated transfer of formatted demographic and clinical information to and from local disease specific registries (and other notifiable registries for patient monitoring and subsequent epidemiological analysis.
DESCRIPTION: The user can export personal...
STATEMENT: Enable the automated transfer of formatted demographic and clinical information to and from local disease specific registries (and other notifiable registries for patient monitoring and subsequent epidemiological analysis.
DESCRIPTION: The user can export personal health information to disease specific registries, other notifiable registries such as immunization registries, through standard data transfer protocols or messages. The user can update and configure communication for new registries.
Show Full Text
Birth Information, Children with Special Healthcare Needs, Genetic information, Immunizations, Registry LinkagesFunctionno
Req-280Clinical Decision Support2013 FormatSystem supports Clinical Decision Support.
Activity Clearance, Children with Special Healthcare Needs, EPSDT, Growth Data, Immunizations, Medication Management, Newborn Screening, Patient Portals - PHR, Primary...
Activity Clearance, Children with Special Healthcare Needs, EPSDT, Growth Data, Immunizations, Medication Management, Newborn Screening, Patient Portals - PHR, Primary Care Management, Registry Linkages, Well Child/Preventive Care
Show Full Text
Headerno
Req-281Documentation of Care, Measurements and Results2013 FormatSystem will document Care, Measurements and Results
Activity Clearance, Children with Special Healthcare Needs, EPSDT, Growth Data, Immunizations, Medication Management, Newborn Screening, Primary Care Management, Registry Linkages,...
Activity Clearance, Children with Special Healthcare Needs, EPSDT, Growth Data, Immunizations, Medication Management, Newborn Screening, Primary Care Management, Registry Linkages, Specialized Scales/Scoring, Well Child/Preventive Care
Show Full Text
Headerno
Req-284Measurement, Analysis, Research and Reports2013 FormatSystem supports measurement, analysis, research and reports.
Activity Clearance, Birth Information, Children with Special Healthcare Needs, EPSDT, Growth Data, Immunizations, Patient Identifier, Primary Care Management, Quality Measures,...
Activity Clearance, Birth Information, Children with Special Healthcare Needs, EPSDT, Growth Data, Immunizations, Patient Identifier, Primary Care Management, Quality Measures, Registry Linkages, Security and Confidentiality, Well Child/Preventive Care
Show Full Text
Headerno
Req-285Administrative and Financial2013 FormatSystem supports Administrative and Financial functions.Children with Special Healthcare Needs, Genetic information, Registry Linkages, Specialized Scales/Scoring, Well Child/Preventive CareHeaderno
Req-286Summary Lists2013 FormatSystems ability to capture summary lists.
Activity Clearance, Child Abuse Reporting, Child Welfare, Children with Special Healthcare Needs, Immunizations, Medication Management, Parents and Guardians and Family...
Activity Clearance, Child Abuse Reporting, Child Welfare, Children with Special Healthcare Needs, Immunizations, Medication Management, Parents and Guardians and Family Relationship Data, Registry Linkages, Well Child/Preventive Care
Show Full Text
Headerno
Req-293Medication and Immunization Management2013 FormatSystem manages Medications and ImmunizationsImmunizations, Medication Management, Registry LinkagesHeaderno
Req-297Clinical Support2013 FormatSystem provides Clinical Support.
Birth Information, Children with Special Healthcare Needs, Genetic information, Immunizations, Parents and Guardians and Family Relationship Data, Registry Linkages, Well...
Birth Information, Children with Special Healthcare Needs, Genetic information, Immunizations, Parents and Guardians and Family Relationship Data, Registry Linkages, Well Child/Preventive Care
Show Full Text
Headerno
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-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-595Report adverse events2013 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.
Immunizations, Registry LinkagesNormative Statementsno
Req-611Synchronize immunization histories with registry2013 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.
Immunizations, 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-673Report summaries: hard copy and electronic2013 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.
Immunizations, Registry 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-694Registry and Directory Services2013 Format
STATEMENT: Enable the use of registry services and directories to uniquely identify, locate and supply links for retrieval of information related to:
- patients and providers for healthcare purposes;
- payers, health plans, sponsors, and...
STATEMENT: Enable the use of registry services and directories to uniquely identify, locate and supply links for retrieval of information related to:
- patients and providers for healthcare purposes;
- payers, health plans, sponsors, and employers for administrative and financial purposes;
- public health agencies for healthcare purposes, and
- healthcare resources and devices for resource management purposes.
DESCRIPTION: Registry and directory service functions are critical to successfully managing the security, interoperability, and the consistency of the health record data across an EHR-S. These services enable the linking of relevant information across multiple information sources within, or external to, an EHR-S for use within an application.
Directories and registries support communication between EHR Systems and may be organized hierarchically or in a federated fashion. For example, a patient being treated by a primary care physician for a chronic condition may become ill while out of town. The new provider's EHR-S interrogates a local, regional, or national registry to find the patient's previous records. From the primary care record, a remote EHR-S retrieves relevant information in conformance with applicable patient privacy and confidentiality rules.
An example of local registry usage is an EHR-S application sending a query message to the Hospital Information System to retrieve a patient's demographic data.
Show Full Text
Child Welfare, Children with Special Healthcare Needs, Growth Data, Immunizations, Registry Linkages, Well Child/Preventive CareFunctionno
Req-772Interchange Standards Versioning and Maintenance2013 Format
STATEMENT: Enable version control according to local policies to ensure maintenance of utilized interchange standards.
Version control of an interchange standard implementation includes the ability to accommodate changes as the source interchange standard undergoes its...
STATEMENT: Enable version control according to local policies to ensure maintenance of utilized interchange standards.
Version control of an interchange standard implementation includes the ability to accommodate changes as the source interchange standard undergoes its natural update process.

DESCRIPTION:
The life cycle of any given standard results in changes to its requirements. It is critical that an organization know the version of any given standard it uses and what its requirements and capabilities are.

For example, if the organization migrates to an HL7 v2.5 messaging standard, it may choose to take advantage of new capabilities such as specimen or blood bank information. The organization may find that certain fields have been retained for backwards compatibility only or withdrawn altogether. The EHR-S needs to be able to handle all of these possibilities.

Standards typically evolve in such a way as to protect backwards compatibility. On the other hand, sometimes there is little, or no, backwards compatibility when an organization may need to replace an entire standard with a new methodology. An example of this is migrating from HL7 v2 to HL7 v3.

Interchange standards that are backward compatible support exchange among senders and receivers who are using different versions. Version control ensures that those sending information in a later version of a standard consider the difference in information content that can be interchanged effectively with receivers, who are capable of processing only earlier versions. That is, senders need to be aware of the information that receivers are unable to capture and adjust their business processes accordingly.
Version control enables multiple versions of the same interchange standard to exist and be distinctly recognized over time.
Since interchange standards are usually periodically updated, concurrent use of different versions may be required.
Large (and/or federated organizations typically need to use different versions of an interchange standard to meet internal organizational interoperability requirements.
For example, the enterprise-wide standard might use HL7 v2.5 for Lab messages, but some regions of the enterprise might be at a lower level.
It should be possible to retire deprecated interchange standards versions when applicable business cycles are completed while maintaining obsolete versions. An example use of this is for possible claims adjustment throughout the claim's life cycle.
When interchange standards change over time, it is important that retrospective analysis and research correlate and note gaps between the different versions' information structures to support the permanence of concepts over time. An example use of this is the calculation of outcome or performance measures from persisted data stores where one version of a relevant interchange standard, e.g., CDA Release 1 captures the relevant data, e.g., discharge data, differently than CDA Release 2.
Show Full Text
Immunizations, Registry LinkagesFunctionno
Req-1134Transmit data on vaccine refusals to IIS2013 FormatThe system SHALL provide the ability to transmit data on vaccine refusals to Immunization Information Systems (IISs using an established and agreed upon messaging standard.Immunizations, Registry LinkagesNormative Statementsno
Req-1139Use established immunization messaging standards2013 FormatThe system SHALL provide the ability to use established and agreed upon messaging standards to transmit and receive data from Immunization Information Systems (IISs and other Health Information Exchanges (HIEsImmunizations, Registry LinkagesNormative Statementsno
Req-1140Send real-time queries on patients to IIS2013 FormatThe system SHALL provide the ability to send standard queries in real-time for immunization data regarding individual patients to Immunization Information Systems (IISsImmunizations, Registry LinkagesNormative Statementsno
Req-1141Access to registries2013 FormatThe system SHOULD provide the ability to add, change, or remove access to registriesImmunizations, Registry LinkagesNormative Statementsno
Req-1145Report adverse immunization events per legal requirements2013 FormatIF the system has the capacity to prepare reports of patient adverse events due to immunizations, THEN the system SHALL prepare the report according to the requirements of local, state and federal agencies as specified by law.Immunizations, Registry LinkagesNormative Statementsno
Req-1147IIS query responses in real-time2013 FormatThe system SHOULD provide the ability to receive real-time electronic query responses from IISs.Immunizations, Registry LinkagesNormative Statementsno
Req-1193Link to Child Welfare registries2013 FormatThe system SHOULD provide an interface or link to child welfare registries to be searchable by name (either child or parent placement, service categories provided, and/or jurisdiction.Child Abuse Reporting, Child Welfare, Registry LinkagesNormative Statementsno
Req-1196Registry support for alerts2013 FormatThe system MAY access registry information (e.g. date of immunization, demographics of subject, name of vaccine to issue alerts within the EHR for specific patient cases.Immunizations, Registry LinkagesNormative Statementsno
Req-1198Birth information to state vital statistics registry2013 FormatThe system SHOULD provide birth information to the appropriate state vital statistics registry.Birth Information, Registry LinkagesNormative Statementsno
Req-1214Child Abuse Reporting and Welfare2013 FormatChild Abuse Reporting, Child Welfare, Primary Care Management, Registry Linkages, Well Child/Preventive CareFunctionno
Req-2011Synchronize immunization histories with registry2015 Priority List
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.
Immunizations, Registry LinkagesNormative Statementyes
Req-2028Use established immunization messaging standards2015 Priority List
A The system shall use the messaging standards established through Meaningful Use requirements to send data to Immunization Information Systems (IISs or other Health Information Exchanges (HIEs
B The system shall use the messaging standards...
A The system shall use the messaging standards established through Meaningful Use requirements to send data to Immunization Information Systems (IISs or other Health Information Exchanges (HIEs
B The system shall use the messaging standards established through Meaningful Use requirements to receive data from Immunization Information Systems (IISs or other Health Information Exchanges (HIEs
Show Full Text
Immunizations, Registry LinkagesNormative Statementyes
Scroll To Top