To go along with @ratchet freak's answer, machine parsing comes more into play when reporting maintenance status and readiness statistics, and for trend analysis - in other words, high-level aggregation and dissection of user-inputted data. At this level, managers are more concerned with the number of aircraft available for use rather than the last time a particular aircraft's tires were
kicked changed. Typically, this is all done using pricy electronic logbook software, and would be used by large organizations with lots of equipment to track and the money to employ such a system.
Take, for example, the United States Army. Its program of record for aviation maintenance and logistics is called Unit Level Logistics System-Aviation, or ULLS-A for short. This software suite automates a lot of the manual forms that the Army uses. At the most basic level, aircraft maintenance is recorded using DA Form 2408-13-1, according to DA Pam 738-751. The time and date of each status is compiled into a daily statistic, which is then rolled up into a monthly report, often only detailing (aside from the hours that aircraft was available for mission) what subsystem was responsible for the majority of each aircraft's downtime. Here's what a blank maintenance form looks like:
As you can see, there are a multitude of blocks, each with its own list of codes. For instance, here is a list of the codes for WHEN DISC (when discovered), from Table 1-6 of DA Pam 738-751:
D Sustainment facility (depot) level repair/overhaul/rebuild
H Phase maintenance inspection (PMI, PPM, PMS2/3 and Reset)
K Unscheduled maintenance
L Maintenance operational check
M Maintenance test flight and/or functional check flight
N AOAP results
O Special inspection, scheduled maintenance
P Diagnostic test (health and usage monitoring device and/or sytem)
T Preflight inspection
U Thru flight inspection
V Post-flight inspection
W Acceptance inspection
X Daily/PMS/PMS1 inspection
Y Intermediate inspection
Z Periodic inspection
However, not all blocks are required to be filled out when using paper logbooks (believe it or not, still in use in some places); in addition to WHEN DISC, HOW REC, MAL EFF, WUC, ACTION CODE, and CAT are optional entries, and in practice never get used. In contrast, these are required fields in ULLS-A, and so the system provides a number of helps to the user so he doesn't have to refer to the manual all the time.
Overall, only these codes (and not the free text fault/remarks block) will be machine-parsed, for the purpose of high-level analysis to determine trends and/or systemic issues affecting the entire fleet.