It is a normal operating procedure in hospitals and other points of delivery of medical services that the attending medical personnel (primary doctor, referring clinicians, nurses, nutritionist, physical therapist, occupational therapist etc.) take quick notes during the course of a patient's admission to track the day to day events in a patient's ongoing care. These notes include but are not limited to, the place/date/time, identity/job title/contact of the author and notation summarizing the author's encounter/intervention with the patient.
Moreover these notes not only form a record of a patient's admission they are also used as a mean of communicating and coordinating a successful healthcare plan between the various teams involved.
currently the notes are most often hand written on paper format in the patients personal set of notes.
Over the of course of the patient' care several notes may be accumulated from different sources. They are usually collected in the document folders of the patient. In the context of a busy healthcare setting these notes are often illegible and fail to give basic information essential to each note.
Moreover their current format makes it difficult to locate specific notes, review the items as a set, collect them together and relate to other data bases containing the patient's medical records. Finally, these notes often form the only copy of the information they contain.
The following detailed description refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements.
In one implementation of the MMMNS, the MMMNS works in the following way. The user of the MMMNS using an EUD inputs the information into the EUD. The EUD sends digitally encoded information into the MMMN-PS using the channel 200. The MMMNS receives this information. The MMMN-PS may store this information, process depending on the type of information and user's request, aggregate, select information based on the combination of indices. The MMMN-PS may communicate using channel 400 or channel 600 with other systems exchanging information about the stored information received from the EUD. The EUD at one point may request the information from the MMMN-PS. The MMMN-PS sends over the channel 200 the response to the request from the EUD.
The EUD may be any type of device comprising software and hardware components capable of input, output, storage and transmission of the electronically encoded information using any type of media and any type of communication channel or communication protocol.
The EUD device in one implementation may be capable of input, output, storage and transmission of textual, visual, image, voice, video, scan, any other form of electric information.
The EUD device in one implementation is also able to support search, query, and any other type of information processing and manipulation on stored or retrieved information.
The communication channel 200 is implemented with any type of wireless or wireline technology capable of supporting the exchange of electronic information between communication devices. The Channel 200 supports the communication using network layers of the standard networking layer model comprising physical, link, data, and higher networking protocol layers or any derived or similar embodiments of the networking protocols resulting from merging or collapsing of networking layers. The communication channel supports the secure information exchange. The security of information exchange is provided by the standard or custom security methods.
The communication channel 400 is implemented with any type of wireless or wireline technology capable of supporting the exchange of electronic information between communication devices. The Channel 400 supports the communication using network layers of the standard networking layer model comprising physical, link, data, and higher networking protocol layers or any derived or similar embodiments of the networking protocols resulting from merging or collapsing of networking layers. The communication channel supports the secure information exchange. The security of information exchange is provided by the standard or custom security methods.
The communication channel 600 is implemented with any type of wireless or wireline technology capable of supporting the exchange of electronic information between communication devices. The Channel 600 supports the communication using network layers of the standard networking layer model comprising physical, link, data, and higher networking protocol layers or any derived or similar embodiments of the networking protocols resulting from merging or collapsing of networking layers. The communication channel supports the secure information exchange. The security of information exchange is provided by the standard or custom security methods.
The data items may include indexing fields, have different information, content, scope, may even be of different format—textual, visual, image, voice, video, scan, any other form of electric information storage would be regarded as permissible data item.
The data items are indexed by several indices. The said Indexes may include but are not limited to: Date, Time, GPS location, Location, Patient's id/name, Medical personnel's ID, name, job title, machine generated patient's number. Indexes are uniquely identifying each stored item with respect to the time, location, patient, doctor entering the item, and other relevant information pertinent. An index may be any unique combination of characters, special characters and numbers or any other signs that can be recognized by the digital device.
In one embodiment the following information may be considered as data item: Place/Date/time/place; Person entering note; patient: hand written note—“Sent to MRI”
In another embodiment the following information may be considered as data item Place/date/time; Person entering note; patient: typed note: “took temperature, took vital signs, discussed with Dr. X the next procedure . . . etc”
In another embodiment the following information may be considered as data item Place/Date/time; Person entering note; patient: voice note on the procedure xxx
In another embodiment the following information may be considered as data item Place/Date/time; Person entering note; patient: video clip of the patient
In another embodiment the following information may be considered as data item Place/Date/time; Person entering note; patient: GPS recording of the patient's location
In another embodiment the following information may be considered as data item Place/Date/time; Person entering note; patient: bar code scan of the medication administered
In another embodiment the following information may be considered as data item Place/Date/time; Person entering note; patient: voice recording of the conversation with the patient
In another embodiment the following information may be considered as data item Place/Date/time; Person entering note; patient: A note from the consultation with the supervising physician
In another embodiment the following information may be considered as data item Place/Date/time; Person entering note; patient: Asked to see patient regarding hypoglycemia. Patient awake in bed and in no acute distress. Vitals: cardiovascular stable, apyrexic, RR 14 and SO2 98 on room air. Impression: pt with hypoglycemia non symptomatic. Plan: repeat glucose check 2. If less then 70 mg/dl give sugar 3. if patient becomes symptomatic please contact at bleep 1234
In another embodiment the following information may be considered as data item Place/Date/time; Person entering note; patient: Ward Round with Dr. John
In another embodiment the following information may be considered as data item Patient post operative day 5 right sided arthroplasty. At bedside patient sitting up and reading. Good mood and affect. Vitals and examination: obs stable, wound dry, minimal signs of inflammation. Patient is mobile and eating and drinking by mouth. Plan: discharge patient today with pain relief and follow up appointment.
Examples [024] to [034] illustrate only exemplary information that can be processed by the MMMNS. The MMMNS is designed to process any type of information related to the patient's medical history not in any way limited, constrained, or defined in form and content by Examples [024] to [034]. In general, the information processed by the MMMNS contains two parts:
INDEX as defined in [0023]
Data as illustrated in exemplar embodiments in [024] to [035]
In the exemplary implementation
The information exchange between systems in [037] may contain but is not limited to the data items listed in Examples [024] to [034] and additional qualified in [035]
In the exemplary implementation
The information exchange between systems in [037] may contain but is not limited to the data items listed in Examples [024] to [034] and additional qualified in [035].
The channel 600 in