DIGI INTERNATIONAL9350 Excelsior Blvd, Suite 700Hopkins, MN 55343, USA+1 (952) 912-3444 | +1 (877) 912-3444Firmware Release NotesDigi CMVersion 1.9.6 (November 12, 2019)INTRODUCTIONThis is the production release of firmware for the Digi CM. These devices provide console management access to various servers, devices, and systems that may be accessed by a serial cableto a console port. These devices feature console management through a console menu or web interface to allow configuration of network settings, serial settings, administration settings, anduser settings. High-end features include Telnet/SSHv1/SSHv2/RawTCP protocols, Local, RADIUS, TACACS+, and LDAP authentication, Port logging through Local, NFS, and Memory cards, PCMCIAslot and configuration, custom menus, keyword monitoring and SMTP/SNMP notification, 10/100 mbps Ethernet network interface, and Digi Discovery server to allow discovery and network configuration from the Digi Discovery Applet.SUPPORTED PRODUCTS∙Digi CM 48KNOWN ISSUESImportant Note: With this release, because of space limitations on the device, the clustering function files have been removed from /bin and must be loaded manually to /usr2.If you are updating from a previous version of CM firmware and you are using clustering, prior to upgrading to the new firmware you can issue the command # cp /bin/cl[us]* /usr2 to migrate thefour necessary files to the new required location without having to upload them after the upgrade.If you need to use the clustering functions, download the CM utilities file (80007071) from the digiweb site and upload the clustering binaries to /usr2 following the instructions for adding clustering inthe utilities file README.txtKNOWN LIMITATIONS∙Web UI, Discovery Applet, and Serial Connection Applet require Netscape4.76 or higher or Internet Explorer 5 or higher.∙The Discovery Applet and Serial Connection Applet also require the Java Runtime Environment (JRE) 1.3 or higher.∙Netscape 4 on Windows: the serial port connection applet will not accept <enter> so the user cannot login through the applet.∙Using cancel button when removing Custom Menus or Copying custom menus causes thepage to be submitted and the menus removed or copied, respectively. To cancel withoutcausing this effect, use the browser's Back button.∙Kerberos authentication has been removed. If you require Kerberos support, download the CM utilities file (80007071) from the digi web site. Copy kinit to the /usr2 dir on the Digi CM.∙If there are a large number of slave units configured the Master can take up to 8 minutes to boot up.∙The ftp client has been removed. If you require ftp support, download the CM utilities file (80007071) from the digi web site. Copy ftp to the /usr2 dir on the Digi CM.ADDITIONAL INFORMATIONWhen using the SUN Java Runtime Environment in Windows, you may need to verify the browser you are using has been enabled with the Java plug-in. To verify, use the following steps:1.Go to Control Panel in Windows (may be accessed through My Computer or1.Start menu)2.If you are using "Category View", click "Switch to Classic View".3.Click Java Plug-In icon. (if this icon does not exist, verify JRE is4.correctly installed)5.Click on the "Basic" tab.6.Verify "Enable Java Plug-In" is checked.7.Click on the "Browser" tab.8.Verify appropriate browser or browsers are checked.9.Click on the "About" tab.10.Verify Java Plug-in version is 1.3 or later.When upgrading releases prior to 1.3.2, Digi advises you to factory default and reconfigure the CM after upgrading the firmware. If upgrading from rev. 1.3.2 or greater, importing configs will workwi th the exception of the “Serial port->User access control” section.Digi CM firmware 1.7.0 or higher now uses the standard Digi Discovery Tool.The original CM Discovery Tool will not work.Revisions previous to 1.7.0 only supports the original CM Discovery Tool.UPDATE CONSIDERATIONSIn order to add compliance with California's Senate Bill No. 327, for information privacy of connected devices, the handling of the root password for newly manufactured products is changing.Products manufactured after January 1, 2020 will no longer use a fixed, default root password. Rather, a per-device, unique password will be assigned during manufacturing, and will be visible on a product label. It will still be possible to change the password for the root user on a per-device basis.Admin user: The admin user is inactive in the new firmware. To activate the admin user, you must first assign a password to the admin user.Products manufactured prior to the adoption of the new product labeling are grandfathered in and will continue to operate as before, with the following exception:AnywhereUSB products manufactured before January 1, 2020, which currently do not have passwords set on them, will have a new default password of "dbps" after upgrading to this firmware. Th e respective username is "root”. THIS NEW DEFAULT PASSWORD SHOULD BE CHANGED, this may be done via the web UI by navigating to Configuration – Security. UPDATE BEST PRACTICESDigi recommends the following best practices:1.Test the new release in a controlled environment with your application before you updateproduction devices.2.Unless otherwise noted, apply updates in the following order:a.Device firmwareb.Modem firmwarec.Configurationd.ApplicationDigi recommends Digi Remote Manager for automated device updates. For more information, go to https:///products/iot-platform/digi-remote-manager. If you prefer manually updating one device at a time, follow these steps from the manual:1.Firmware update processTECHNICAL SUPPORTGet the help you need via our Technical Support team and online resources. Digi offers multiple support levels and professional services to meet your needs. All Digi customers have access to product documentation, firmware, drivers, and knowledge base and peer-to-peer support forums. Visit us at https:///support to find out more.CHANGE LOGVERSION 1.9.6 November 11, 2019This is a mandatory release.MD5 Checksum69BCC515D27B5994F4044D45CA48A7E9 *cm48SHA-256ED5FF872255FE8E3ED40637855F1240FF4A099BD3BA054F8509FF087F05747A0 *cm48NEW FEATURES1.Added support for California's Senate Bill No. 327. Product manufactured after January 1,2020 will have a unique password.ENHANCEMENTSNoneSECURITY FIXESResearchers have discovered new denial-of-service (DoS) vulnerabilities in Linux and FreeBSD kernels, including a severe vulnerability called SACK Panic that could allow malicious actors to remotely crash servers and disrupt communications, according to an advisory.“Th e vulnerabilities specifically relate to the Maximum Segment Size (MSS) and TCP Selective Acknowledgement (SACK) capabilities. The most serious, dubbed “SACK Panic,” allows aremotely-triggered kernel panic on recent Linux kernels,” the advisory stated. Th isvulnerability also goes back a long time (since Linux v2.6.29, that was released 10 years ago).“The issues have been assigned multiple CVEs: CVE-2019-11477 is considered an Important severity, whereas CVE-2019-11478 and CVE-2019-11479 are considered a Moderate severity”. BUG FIXESNoneVERSION 1.95 May 10, 2010∙Added option to sync RTC with system time.∙Fixed a problem where The Web UI or Configmenu don't show the current Remote auth type for the CLI.∙Fixed a problem where Port locks up when accessing an Aix server via ssh and remote ports.∙Fixed a problem where Port access via web java app locks user account after only one failed login attempt.。
2016Progress Notes Toolkit: A guide for Personal Support Workers serving people with disabilities in OregonPROGRESS NOTESContentsAbout this Guide (3)Progress Notes (3)Purpose (3)What to Include (4)Examples (5)Additional Considerations (6)Privacy (6)Reporting Incidents (6)Reporting Abuse (6)Tools (7)Checklist (7)Resources (8)References (8)Activities (9)About this GuideOregon uses Medicaid dollars to provide supports for people with disabilities. Progress notes are one way to be sure funds are used appropriately to meet the needs of people served. The goal of this guide is to help Personal Support Workers (PSWs) write useful progress notes. This document is online at the Office of Developmental Disabilities Services website for Provider Resources.Website/DHS/SENIORS-DISABILITIES/DD/PROVIDERS-PARTNERS/Pages/index.aspx Using this Guide: This guide can be used as one complete document, or each section can be used individually. Quick reference pages, resources and learning activities are included.Progress Notes A progress note is written information that describes what you did to meet the needs of the person you serve. You must document your PSW activities in progress notes.PurposePaychecksYou must turn in a progress note with each timesheet. Your payment could be delayed until missing progress notes are turned in.BillingMedicaid requires th at PSW providers keep records to document “the extent of services the provider furnishes to reci pients”. Progress note s are evidence that the service was provided. They are important for payment of service claims.Legal RecordYour notes become part of the person’s permanent legal record. Progress notes may be used in legal proceedings, audits or investigations. They can also provide a paper trail in case of conflict or difficult situations.MonitoringServices Coordinators and Personal Agents review progress notes to see how supports are working. They document progress towards a person’s Individual Support Plan (ISP) goals and desired outcomes. Your progress notes are a valuable source of information.Quality CareQuality progress notes are impo rtant to a person’s care. The team gains information from your records. At times this may include support staff, medical staff, therapists, and others.A Person’s storyProgress not es help map out a person’s progress. Your notes are part of their story.Turn in progress notes with your timesheets. They can be on a separate page. Submitting progress notes in a timely manner helps keep the team informed. Please type or write clearly. What to IncludeProgress notes are a summary of what occurred. Include your name, the name of the individual, date of service and date of progress note.Progress notes also need to explain what activity you did. Make sure to describe the following: o What actions you took and what specific support you provided.o What you did to help meet the person’s health and safety needs.o What you did to help meet the person’s other support needs.(examples: managing medication, preparing food, guiding for street safety, usingassistive devices, communication strategies, behavior supports, or safety plans)o Any progress towards the person’s ISP goals and outcomes.o Is the plan working? Are there any new needs?NOTE:Refer to your Service Agreement to see what tasks you are authorized to provide. The support you provide should address the needs and goals listed in the Service Agreement. You may also talk to your employer or the person’s Service s Coordinator or Personal Agent.ExamplesPSWs may help with a variety of activities at home and in the community. These could include: ∙eating and drinking ∙ dressing∙ grooming such as hair brushing ∙ bathing∙ hygiene such as teeth brushing ∙ mobility such as walking or getting into bed∙ bathroom supports ∙ communication∙ cognition (thinking and understanding) ∙ social interactions ∙behavior∙ housekeeping ∙ laundry∙ shopping and money management ∙ transportation∙ medication management ∙preparing mealsExamples of supports that PSWs may provide: ∙ Giving cues to help a person complete an activity. ∙ Doing an activity because a person is unable to do so. ∙ Monitoring to see if help is needed. ∙ Offering encouragement and support. ∙ Redirecting a person.∙Taking care of personal items, supplies, or equipment.NOTE: Be sure to use details. Be specific. Progress notes should be unique to the personserved. Notes should never be copied or “cookie cutter”. Even if two people have similar support needs, their notes should be personal.Additional ConsiderationsPrivacyProgress notes should not include the names of other people served. This is for privacy purposes. You can work with the Services Coordinator or Personal Agent to learn how to send in progress notes securely. The Oregon Home Care Commission offers free classes to PSWs. These classes cover many topics including confidentiality. Please see the Resources section for more information.Reporting IncidentsYou must provide notification to the case management entity if unusual incidents occur. Be sure to report what happened before, during and after the incident.An Incident Report is the written report of any:∙injury∙accident∙act of physical aggression∙use of protective physical intervention, or∙unusual incident involving an individualAn Unusual Incident is any incident involving an individual that includes:∙serious illness or accident∙death∙injury or illness requiring inpatient or emergency hospitalization∙ a suicide attempt∙when an individual contacts the police or is contacted by the police∙ a fire requiring the services of a fire department∙an act of physical aggression, or∙any incident requiring an abuse investigationPer OAR 411-317 General Definitions Reporting AbuseNote: Personal Support Workers are mandatory abuse reporters.You can call 1-855-503-SAFE (7233) to report abuse or neglect of any child or adult to the Oregon Department of Human Services. See the reference section for more information.Tools ChecklistThe note describes:What occurred during the dates for that timesheet.What you did to support the person.What you did to help the person make progress towards ISP outcomes.How the person’s needs are being met.Any new needs that may have come up.Any incidents that occurred.Any problems completing your work, including if someone does not wantsupport.Professional writing:State the facts. Avoid personal opinions.Use respectful language.Avoid slang or abbreviations.TIP: Writing notes soon after service occurs helps you remember the details of the interaction. Submitting them in a timely manner helps keep the team updated.ResourcesFor more information, please see the following resources:Person-Centered Language and Practices1. Core Competency eLearning modules for Direct Support ProfessionalsDHS - DD - DSP 106: Dignity, Respect, and Person Centered Language - C05231https:///2. The Learning Community for Person Centered Practices/Incident Reporting1. Core Competency eLearning modules for Direct Support ProfessionalsDHS - DD - DSP 127: Incident Report Requirements - C05242https:///Abuse Reporting1. Oregon Department of Human Services/DHS/abuse/Pages/index.aspx2. Oregon Adult Abuse Prevention and Investigations elearning moduleDHSOHA - OAAPI - Mandatory Abuse Reporting: People with Developmental Disabilities https:///Confidentiality Practices and other PSW training opportunities1. Oregon Home Care Commission/DHS/SENIORS-DISABILITIES/HCC/PSW-HCW/Pages/OHCC-Training.aspx 2. Developmental Disabilities Provider and Partner Resources webpage/DHS/SENIORS-DISABILITIES/DD/PROVIDERS-PARTNERS/Pages/index.aspx ReferencesOregon Administrative Rule 411-375Independent Providers Delivering Developmental Disabilities ServicesOregon Administrative Rule 411-317G eneral Definitions and Acronyms for Developmental Disabilities ServicesCenters for Medicare & Medicaid Services Code of Federal Regulations 431.107(b)(1-2) Documentation Requirements for Providers of Medicaid Services2015-2019 Collective Bargaining AgreementArticle 8 - Payroll/Voucher Systems, Section 1. Properly Completed Voucher or TimesheetActivitiesUse the following activity descriptions to help guide discussions and learning sessions. The overall learning objective is for PSWs to be able to complete progress notes appropriately.1. Fill in the Blank: Lead a group brainstormingsession. Share the statement below with participantsand ask for words to fill in the blank. See sidebar forpotential answers.Progress notes should be ______________.Learning Objective: This activity helps PSWs find personalmotivation for completing quality documentation.2. Self Checks: Individually or in groups, askparticipants to address the following prompts.∙Describe why documentation is important. What are some examples in your own experience?∙Do you have a copy of your Service Agreement for the person you support?Describe what a Service Agreement is. What are some of the needs andgoals/outcomes listed for a person you support? Why are these important?Learning Objective: This activity helps PSWs connect broad documentation requirements with their individual work responsibilities.3. Strengthening Progress Notes: Share a scenario from the examples below.One by one, reveal each successive example of a progress note for that scenario.Facilitate discussion between each example. Individually or in groups, ask participants to think of ways to strengthen the progress note.Discussion should highlight the best practices of documentation. For example, eachadditional progress note adds information about the Personal Support Worker’s actions, how the individual’s needs are being met, and progres s toward the individuals goals.PSWs should try to add as much detail as possible, as shown in the third examples.You can repeat this activity with other potential scenarios of your own.Learning Objective: This activity gives PSWs an opportunity to apply their knowledge and practice writing strong progress notes.Strengthening Progress Notes activity examplesScenario #1: PSW took Janea to the store.Progress note examples:I assisted Janea with shopping.*discussion*I assisted Janea with grocery shopping, budgeting, making change, talking with people, and transportation.*discussion*I assisted Janea twice this month with grocery shopping. I helped her at the store with selecting needed items, staying within budget, counting correct change, communicating with the cashier and transportation to and from the store. Janea seems to be making progress on her goal of managing her money. She was able to stay within her budget this month. I reminded her to use her grocery-shopping list and helped her fill out her checkbook ledger.*discussion*Scenario #2: PSW took Janea bowling.Progress note examples:I supported Janea at the bowling alley.*discussion*I supported Janea at the bowling alley. I provided social and communication supports while bowling.*discussion*I assisted Janea with social integration and communication at the bowling alley once this month. I helped her prepare for conversation with the cashier. I also provided reminders for social rules at the bowling alley and safety rules when talking to people she meets. Janea said she was “nervous” about talking to people but later said she “had fun bowling.” She seems to get more comfortable each trip we take.*discussion*Scenario #3: PSW helped Janea with getting ready.Progress note examples:I helped Janea every morning before work with hygiene.*discussion*I helped Janea with hygiene in the morning before work. I helped with brushing herteeth, showering, brushing her hair and tying her shoes.*discussion*I helped Janea in her home with hygiene every morning before work. I re-brushed herteeth after she brushed them to prevent cavities since she has a hard time reaching the back teeth. I also adjusted the water temperature in the shower and assisted withwashing her hair. I reminded her to use soap for washing her body. I helped her brush and style her hair appropriately for work. I provided reminders to pick out clean clothes for work and I tied Janea’s shoes.Janea had two incidents of overnight incontinence this week. She has needed extrahelp with changing the bed on those days. This is less than last week (6 incidents) since she started her new medication. She has a follow up appointment with her doctor next month. I filled out the tracking sheet to be shared with the doctor.*discussion*Note:This guide is intended to provide general information only and be used as a tool in developing strong documentation skills. This information is not a substitute for relevant regulations. Administrative rules and policies are subject to change and supersede information found in this guide.December, 2016Page 11 of 11。
QUALCOMM ATHEROS COMMUNICATIONS, INCQCA8829 Release NotesV1.0.8Revision HistoryTable of Contents1About this Release (4)2Included in this Release (5)3Installation Instructions (6)4Testing Status of this Release (7)5New Features (8)5.1In this Release (8)5.1.1PON Features (8)5.1.2Bridge Features (8)5.1.3Traffic Management Features (9)5.1.4Detailed Statistics is supported (9)5.2In Previous Releases (9)6Limitations & Restrictions (10)6.1New (10)6.1.1Character input in CLI is case insensitive. (10)6.1.2Error prompts in CLI is incomplete. (10)6.1.3Input parameter validity from CLI is incomplete. (10)6.1.4Leave mode configuration from OAM can’t be saved (10)6.1.5Information about technology ability and advertised technology ability of ONUGE port is incomplete. (10)6.1.6Unsupported IGMP control type of “GDA_SA_MAC” is not deleted (10)6.1.7Upstream QoS of high priority traffic can’t be guaran teed when congestionoccurs. (10)6.2Propagating - Updated (11)6.3Propagating - Unchanged (11)7Compatibility with Previous Releases (12)Contacting Qualcomm Atheros (13)1 About this ReleaseThis is a Development release of QCA8829 Software. This release is intended for use with the QCA8829 Rev A device.Qualcomm Atheros releases are defined as follows:∙The mm.nn.xx number is used to denote the major (mm), minor (nn) and revision (xx) release numbers. An increment in the major release number indicatessubstantially architecture or API changes. An increment in the minor release number indicates new functionality or significant bug fixes. An increment in the revisionrelease number indicates bug fixes and small improvements that are intended to be released to customer as backwards compatible patch.∙Dev (Development) – Functionally incomplete, partially verified by the SW team, and not fully tested by Qualcomm test group. The Development release is intended for evaluation and initial development by early adopters and sometimes provided to specific customers as an indication of final hardware and SW capabilities.∙Alpha– Alpha features functionally complete, fully verified by the SW team, and undergone super-critical test by test group which is intended to test core functionality but is not comprehensive nor does it test corner cases.∙Beta– Has undergone critical validation by test group, which is intended to test the basic functionality of the SW with comprehensive tests of any new functionality.∙Prod(Production) – Has undergone complete validation by test group, which is a full comprehensive suite, set of tests against the features/requirements and error scenarios.2 Included in this ReleaseThis release of the QCA8829 SW consists of the following components:This release of the QCA8229 SW includes the following files:3 Installation InstructionsBecause of development limitation QCA8829 software version must be firstly upgraded to a temporary version (v1.0.5) and then upgraded to v1.0.8. Detailed procedure to upgrade QCA8829 firmware can be found in document of QCA8829 software guide manual.4 Testing Status of this Release5 New Features5.1 In this Release5.1.1 PON FeaturesIEEE 802.3ah standard and China CTC standard compliantLLID-based decryption∙AES-128 CFB mode∙CTC Triple-ChurningPacket-based FEC, RS (239, 255)Support SCB channelDBA engine for queue set report5.1.2 Bridge Features5.1.2.1 VLANSupport 802.1q and 802.1ad VLAN with double tagSupport VLAN translation based on dedicated VLAN ID or VLAN range including SVLAN, CVLANTotal 64 VLAN entries supported5.1.2.2 ARLSupport upstream MAC learning, wire-speedSupport MAC filter, bindingTotal 64 entries supported.5.1.2.3 Packet ClassificationMask and Rule based Packet classification into the first 80Byte of PacketSupported classification field including VLAN, 802.1p, Ethernet type, SA/DA MAC address, SA/DA IP address(IPv4/IPv6) and TCP/UDP port/range.Supported action including ACL, filter, copy, send to CPU, outer VLAN tag remark, 802.1p override and I_COS mark/remark5.1.2.4 Multicast FeatureSupport IPv4 IGMP v1/v2Total 64 multicast group entries5.1.2.5 Multicast/Broadcast control5.1.2.6 Flexible Service to LLID BindingSupport VLAN-based flow to LLIDSupport VLAN+COS based flow to LLID5.1.3 Traffic Management FeaturesTotal 32 queue for 8 LLID port8 queue for UNI GE port8 queue for CPU port, 4 queues for upstream traffics and 4 queues for downstreamtrafficsCos-based enqueue /dequeue, flexible traffic type mapping into different queuePer-port/per-queue based traffic shaping with single token bucket limiterSP, DWRR, SP+DWRR Schedule for PON Upstream, GE DownstreamSP schedule for CPU portPer-queue based inbound policingQueue-level and LLID port level ShaperWRED, tail drop queue management5.1.4 Detailed Statistics is supported5.2 In Previous ReleasesN/A6 Limitations & RestrictionsThis section describes the limitation and restrictions for this release.6.1 New6.1.1 Character input in CLI is case insensitive.All character inputs in CLI will be translated into lowercase character. Therefore some system information configurations, such as hostname, location, user name and password will all be translated into lowercase character.6.1.2 Error prompts in CLI is incomplete.For some error commands executed in CLI, the error prompts are not clear enough. For example, there is an input parameter missed. But the prompts are “invalid input detected”, not “incomplete command”.6.1.3 Input parameter validity from CLI is incomplete.There is no any error prompt when some commands that don’t exists or error commands are input.6.1.4 Leave mode configuration from OAM can’t be saved.The save to leave mode configuration can’t take effect after system is reset. It keeps initial value.6.1.5 Information about technology ability and advertisedtechnology ability of ONU GE port is incomplete.ONU GE port supports speed of 10M. But the information isn’t shown when GE port abilities are got.6.1.6 Unsupported IGMP control type of “GDA_SA_MAC” is notdeleted.IGMP control type of “GDA_SA_MAC” is not supported. However the information still exists when IGMP abilities are got.6.1.7 Upstream QoS of high priority traffic can’t be guaranteedwhen congestion occurs.6.2 Propagating - Updated6.3 Propagating - Unchanged7 Compatibility with Previous ReleasesContacting Qualcomm Atheros。
disclosure notesDisclosure NotesDisclosure notes, also known as footnotes or notes to the financial statements, are important additions to the financial statements that provide additional information and explanations for various items. These notes are an integral part of the financial reporting process and play a crucial role in enhancing the transparency and understandability of financial statements. In this article, we will discuss the key types of disclosure notes and the information they typically include.1. Summary of Significant Accounting Policies: This note providesa summary of the significant accounting policies followed by the company in preparing its financial statements. It includes information on the basis of measurement, recognition criteria, and valuation methods adopted for various assets, liabilities, revenues, and expenses.2. Contingent Liabilities: This note discloses any contingent liabilities that may have a significant impact on the company's financial position and performance. Contingent liabilities are potential obligations that arise from past events but are not recognized as actual liabilities in the financial statements. Examples include pending lawsuits, warranty claims, and potential tax assessments.3. Related Party Transactions: This note discloses any transactions with related parties that could have influenced the financial position or performance of the company. Related parties includekey management personnel, entities controlled by the company, and close family members of key management personnel. The note provides details of the transactions, their nature, and the amounts involved.4. Segment Reporting: If a company operates in multiple business segments, this note provides information on the operating performance and financial position of each segment. It includes details such as revenues, expenses, assets, and liabilities for each segment. Segment reporting helps users of financial statements understand the risks and opportunities associated with different segments of the company's business.5. Employee Benefits: This note provides information on the company's employee benefit plans, such as pensions, post-employment healthcare, and share-based payment arrangements. It includes details of the types of benefits provided, the measurement methods used, and the related costs recognized in the financial statements.6. Income Taxes: This note provides information on the company's income tax obligations and any potential tax disputes or uncertainties. It includes details of the current and deferred tax expenses, tax losses carried forward, tax credits, and any unrecognized tax benefits.7. Leases: This note discloses the company's leasing arrangements, including details of the lease terms, lease payments, and the impact of leases on the financial statements. It also includes information on significant leasing commitments that are not recognized asliabilities in the balance sheet.8. Fair Value Measurements: If the company has financial instruments that are measured at fair value, this note provides information on the valuation techniques used and the level of hierarchy within the fair value hierarchy. It also discloses any significant unobservable inputs used in the fair value measurement process.9. Subsequent Events: This note discloses any significant events or transactions that occurred after the balance sheet date but before the financial statements are authorized for issue. Examples include the sale of a significant asset, the settlement of a lawsuit, or a major acquisition.10. Going Concern: If there are any material uncertainties related to the company's ability to continue as a going concern, this note provides information on the key assumptions used by management in assessing the company's ability to meet its obligations and the extent to which the financial statements are prepared on a going concern basis.These are just some examples of the types of disclosure notes that can be found in financial statements. The specific contents of disclosure notes may vary depending on the nature of the company's operations, industry, and regulatory requirements. Overall, disclosure notes are essential for providing relevant and reliable information to users of financial statements, enabling them to make informed decisions about the company's financial position and performance.。
