CPAPtalk.com

ok what is the extension of the xml file, is this information on my cpap machine remstar auto series m. Is this file legally my property.

The extension is xml

There is no way you are going to get the electronic file from your RT, and the xml file is a database with other patient records. Next time, download the data yourself before you go in, or better yet, just give a printed report to the RT so she can't erase your card. Either way, its amazing to me anyone has a professional actually looking at this data and making recommendations. No one has ever asked for my data card.

the xml file is a database with other patient records

The EncorePro SQL Database may contain multiple patients but the EncorePro exported XML file is by Patient Name and, therefore, only contains data for a single patient.

My EncorePro SQL Database only contains one patient (me). I suspect most Sleep Drs., Sleep Labs, DMEs, etc., that are using EncorePro, have multiple patients stored in their EP database. Each requesting patient would only get their data in an Exported XML file.

I know a patient record can be exported and imported. I don't believe that record can be merged with an existing record. Is that correct? In other words, even if you could somehow persuade the RT to export your record, it would be a second patient record in your home encorepro database. (never done it, so I don't have a clue). I question how valuable the data could possibly be. There would not be more than one week of detailed data, and the rest would be compliance. In the overall scheme of things, I could live without any of my many weeks of recorded data.

I don't believe that record can be merged with an existing record. Is that correct? In other words, even if you could somehow persuade the RT to export your record, it would be a second patient record in your home encorepro database. (never done it, so I don't have a clue).

I don't believe that you can import XML data for a patient and have EP merge it with an existing patient of the same name. I've had no reason to give it a try so don't know for sure. Give it a try and see what happens.

It is easy, however, to create a new You (just give yourself a different name). Use the EP patient input data screens to describe the new you and save your input. Use a newly formatted card (use MyCPAP card utility) to collect the machine data for the new You. Insert the smartcard into the reader and it will prompt for the patient name (there will now be two patients and with an unformatted card it won't know whose data is on it). Select the new You as the patient and the new smartcard data will be processed and stored in a set of EP SQL tables associated with the new You. If you don't format the card after the download to EP, it will contain the new You name on the smartcard for subsequent downloading.

One benefit of defining new Yous is to limit the size of your patient XML file that you, hopefully, are exporting on a frequent (good to have a backup) basis. I, for example, plan to setup a new Me come January 1, 2010. By doing so, I will start again at a small file size for my exported XML file.

BTW, smartcards are inexpensive. I have six and bought two for $15 total including S&H back in May (also received one each with my two machines). For someone that will be getting the software and card reader in a few weeks, it may make sense to buy a few smartcards, one for each week, so that all the historic detail data will be available when the software arrives.

Sleeprider wrote:I know a patient record can be exported and imported. I don't believe that record can be merged with an existing record.

How hard would it be to export your record from home, paste the missing data from the lab's version of your record into your home export file, and then import the whole shebang back into your home profile? XML is pretty easy to work with.

How hard would it be to export your record from home, paste the missing data from the lab's version of your record into your home export file, and then import the whole shebang back into your home profile? XML is pretty easy to work with.

I have some familarity with XML but not a lot. I am a novice with this language. Why don't you take a look at the EP exported XML file and see what it would require in skill and time to paste in the new data. Please note that the XML schema (created by Excel 2003) for the EP exported XML file has close to 100 entries. Would this # of entries make it easier or harder to paste in the new data?

cinco777 wrote:Would this # of entries make it easier or harder to paste in the new data?

It's still Ctrl-C and Ctrl-V!

(sorry)

This is just a guess, but I'm assuming it would work like this:

Let's call the file that you export from your own profile File 1 and the file that your RT exports for you File 2.

I assume File 1 contains a long series of records for the daily data, but has a "hole" in the series where the 6 mos of missing data should be.

Similarly, File 2 has a long series of records for the six months of data.

If you examine the records and compare one record (which might consist of a whole bunch of XML "fields"--actually called "elements") in File 1 with a record in File 2. If there's anything in the records that identify the patient (patient ID, patient number, name, or whatever), then you'll have to Find & Replace All to make the identifier in File 2 match File 1.

Then examine the date ranges carefully and copy all of the records for the target date range from File 2 and paste them into File 1.

If you're right about the amount of data, you might have to press Ctrl-V real hard.

Back up all of your data first and only fiddle around with copies of the files.

If the records aren't easy for you to read at first, Google some articles that explain basic XML concepts. And if the records aren't nicely formatted and indented (which makes a HUGE difference), then Google for a good "xmllint" utility that will parse and format the records for you.

You might want to take a look at the EP exported XML file. My novice view is that it is a hodgepodge! and won't have the single "hole" that you are looking for. I don't need such a capability so someone that does will, if technically inclined, need to pursue a solution.