The MedOne Web Service is designed to allow you to make secured HTTPS REST calls to fetch various bits of information about patients known to our system. The results are available in either XML or JSON. You can specify which format by either setting the Accepts header in your request or by prefixing your request with a .xml or .json, as the case requires. For example:
$ curl -H "Accept: application/xml" \
GET https://server:port/api/v1/patientlookup?LastName=Smith
$ curl GET https://server:port/api/v1/patientlookup.xml?LastName=SmithWill return the same thing, an xml formated data set. Similarly:
$ curl -H "Accept: application/json" \
GET https://server:port/api/v1/patientlookup?LastName=Smith
$ curl GET https://server:port/api/v1/patientlookup?LastName=Smith
$ curl GET https://server:port/api/v1/patientlookup.json?LastName=SmithWill return the same things, but formated as JSON.
Filename extension takes precedence over the accept header.
JSON is the default if no format is specified other ways.
Every call, except for patientlookup, can takes at up to three parameters.
| Parameter | Type | Optional |
|---|---|---|
| id | long | no |
| T1 | ISO-8601 UTC | yes |
| T2 | ISO-8601 UTC | yes |
One is the ID that you found in patient lookup, the others are time values. They are given the name T1 and T2. They need to be in ISO-8601 UTC values. For instance:
GET https://server:port/api/v1/patient/{id}/smokingstatus?
T1={datetime}&T2={datetime}The above example shows two parameters being passed in.
If you provide no time stamps, we assume you are interested in a single point in time and that time is now. If you provide a T1 value only, we will use that as the single time point that you wanted and provide information that was current as of that time. If you provide a T1 and T2 we will return all the states the concept had between time T1 and T2. Providing just a T2 is the same as not providing anything, and we will return data based on the current state of the patient.
This is not true for the CCDA call you will read about below.
Every call returns a list of values. If no values are found, an empty list is returned. This is not true for the CCDA call you will read about below. Any other errors, such as invalid, non parseable date/time values, or T1 being > than T2, will generate a http 400 error and will return data describing the error. An example is below.
All requests are made with standard http GET calls, and the usual result codes (200 OK, 404 Not found, etc) are used in the usual way. The requests can be made with any tool that can help make http get calls for you.
Many of the calls that take two timestamps as parameters are designed to return timestamped lists of values. These all have a very similar structure. The calls return a list of objects that contains a when and a value property. The when value will contain a ISO8601 UTC date time, and value will be a list of objects that represent the state of that resource at that time.
Currently, the MedOne systems API is designed to run inside the hospitals security domain and will only allow people to interact with it that have appropriate credentials in the Active Directory for the domain. The MedOne Systems API exposes a website that will allow you, once properly credentialed and belonging to the correct groups, request tokens that will allow you to make API calls.
These tokens should be passed to the web service using the Authentication Bearer token syntax shown below.
Authentication: Bearer eyJhbGciOiJQQkVTMi1IUzUxMitBMjU2S1ciLCJlbmMiOiJBMjU2Q0JDLUhTNTEyIiwicDJjIjo4MTkyLCJwMnMiOiJJcFFBRVZVU0U1RjVoN0FRIiwiemlwIjoiREVGIn0.iRIFyHKbD-1BOLVsab9en5Tx-JieD0lz5qUXrACQ6ttgvjZTfbqEcQXsDkObY_5my00O6N7ij8qiktugUJTeoT7_FtOxfJuT._QQMgld5npMg9_KflKCrPw.vrAWM7eZLGMSrMnjhMSiBGorFUGWztUq5r-PNjtHlW_S5Lw0cJm985Of9TIO9QAOUc23cVSzQk0UK4JcOPGK2Vxiv_1uIJDnaEFYkfqKHpoHviYhWYrko9RXHmdFvCr_oY9l2QWATEzd-bR1Rntssc9xK-nrze2_c5R759qUc8BBlaKsTU1BHXNwhKpT-yZu.Bmgxzf29YNmU7vDUIYloG8H3sn3dIXgu62qI2CtIu7MIf the header contains such a token, and it is validated as being correct, your api call be allowed to complete.
All calls are currently rooted at the url /api/v1/. We may will leave that out of the following discussion for brevity’s sake.
GET https://server:port/api/v1/patientlookup?LastName={string}&FirstName={string}&
MiddleName={string}&DateOfBirth={date}&SSN={string}&EXMRN={string}&ID={long}All of the parameters are optional, but at least one must appear. Records that match all provided filters will be returned.
DateOfBirth queries are matched using exact date matches. The date value should only be date information and should be presented in a YYYY-MM-DD format.
ID queries are done using exact equality matches as well.
All other queries are matched using a case insensitive partial string match. In short, if the string provided exists anywhere inside the target string it will match. For those that understand SQL, think of it as a like '%value%' query. ie LastName=mith would match Smithers, and Dolmithy, etc.
GET https://server:port/api/v1/patientlookup?LastName={string}&FirstName={string}&
MiddleName={string}&DateOfBirth={date}&SSN={string}&EXMRN={string}&ID={long}Returns a list of objects. Details of objects provided below.
[
{
"id": 10035861,
"externalMedicalRecordNumber": "H000560407",
"lastName": "WELLERS",
"firstName": "DEBRA",
"middleName": "J",
"dateOfBirth": "1958-03-17",
"socialSecurityNumber": "12345677"
}
]<?xml version="1.0"?>
<ArrayOfPatientLookupDetails xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<PatientLookupDetails>
<Id>10035861</Id>
<ExternalMedicalRecordNumber>H000360407</ExternalMedicalRecordNumber>
<LastName>WELLERS</LastName>
<FirstName>DEBRA</FirstName>
<MiddleName>J</MiddleName>
<DateOfBirth>1958-03-17</DateOfBirth>
<SocialSecurityNumber>112343456</SocialSecurityNumber>
</PatientLookupDetails>
</ArrayOfPatientLookupDetails>| Property | Type |
|---|---|
| Id | long |
| ExternalMedicalRecordNumber | string |
| LastName | string |
| FirstName | string |
| MiddleName | string |
| DateOfBirth | string (date formatted) |
| SocialSecurityNumber | string |
GET https://server:port/api/v1/patient/{id}/commonYou can pass T1 and T2 parameters into this call as all of the others, but due to how this data is stored in our system you will only ever get one result.
Returns a list of objects. Details of the objects are detailed below.
[
{
"id": 10035861,
"externalMedicalRecordNumber": "H000360407",
"lastName": "WELLERS",
"firstName": "DEBRA",
"middleName": "J",
"dateOfBirth": "1958-03-17",
"socialSecurityNumber": "2222222222",
"sex": "F",
"languageDeclines": null,
"preferredLanguage": "en",
"raceCodes": "1014-0,1015-7,2106-3",
"raceDescriptions": "Lipan Apache,Mescalero Apache,White",
"raceRollupCodes": "1002-5,2106-3",
"raceRollupDescriptions": "American Indian or Alaska Native,White",
"ethnicityCodes": "2144-4,2145-1,2186-5",
"ethnicityDescriptions": "Valencian,Canarian,Not Hispanic or Latino",
"ethnicityRollupCodes": "2135-2,2186-5",
"ethnicityRollupDescriptions": "Hispanic or Latino,Not Hispanic or Latino"
}
]<?xml version="1.0"?>
<ArrayOfPatientCommonData xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<PatientCommonData>
<Id>10035861</Id>
<ExternalMedicalRecordNumber>H000360407</ExternalMedicalRecordNumber>
<LastName>WELLERS</LastName>
<FirstName>DEBRA</FirstName>
<MiddleName>J</MiddleName>
<DateOfBirth>1958-03-17</DateOfBirth>
<SocialSecurityNumber>2222222222</SocialSecurityNumber>
<Sex>F</Sex>
<LanguageDeclines xsi:nil="true" />
<PreferredLanguage>en</PreferredLanguage>
<RaceCodes>1014-0,1015-7,2106-3</RaceCodes>
<RaceDescriptions>Lipan Apache,Mescalero Apache,White</RaceDescriptions>
<RaceRollupCodes>1002-5,2106-3</RaceRollupCodes>
<RaceRollupDescriptions>American Indian or Alaska Native,White</RaceRollupDescriptions>
<EthnicityCodes>2144-4,2145-1,2186-5</EthnicityCodes>
<EthnicityDescriptions>Valencian,Canarian,Not Hispanic or Latino</EthnicityDescriptions>
<EthnicityRollupCodes>2135-2,2186-5</EthnicityRollupCodes>
<EthnicityRollupDescriptions>Hispanic or Latino,Not Hispanic or Latino</EthnicityRollupDescriptions>
</PatientCommonData>
</ArrayOfPatientCommonData>| Property | Type |
|---|---|
| Id | long |
| ExternalMedicalRecordNumber | string |
| LastName | string |
| FirstName | string |
| MiddleName | string |
| DateOfBirth | string (date formatted) |
| SocialSecurityNumber | string |
| Sex | string |
| LanguageDeclines | nullable boolean |
| PreferredLanguage | string |
| RaceCodes | string (SNOMED codes, comma delimited) |
| RaceDescriptions | string (comma delimted) |
| RaceRollupCodes | string (SNOMED codes, comma delimited) |
| RaceRollupDescriptions | string (comma delimted) |
| EthnicityCodes | string (SNOMED codes, comma delimited) |
| EthnicityDescriptions | string (comma delimted) |
| EthnicityRollupCodes | string (SNOMED codes, comma delimited) |
| EthnicityRollupDescriptions | string (comma delimted) |
GET https://server:port/api/v1/patient/{id}/problems?T1={datetime}&T2={datetime}Returns a list of objects. Each object is composed of a timestamp and a value. The value is a list of objects detailed below.
[
{
"when": "2017-07-10T18:53:55.3993956Z",
"value": [
{
"conceptId": 89765005,
"problem": "Tobacco dependence syndrome",
"status": "Chronic",
"presentOnAdmission": false,
"diagnosedDateTime": null,
"inactiveDateTime": null
}
]
},
{
"when": "2017-07-10T18:58:08.6447708Z",
"value": []
},
{
"when": "2017-08-02T14:32:45.6399171Z",
"value": [
{
"conceptId": 213026003,
"problem": "Malignant hyperpyrexia due to anesthetic",
"status": "Chronic",
"presentOnAdmission": false,
"diagnosedDateTime": null,
"inactiveDateTime": null
},
{
"conceptId": 29857009,
"problem": "Chest pain",
"status": "Acute",
"presentOnAdmission": false,
"diagnosedDateTime": null,
"inactiveDateTime": null
}
]
},
{
"when": "2017-09-12T14:30:31.691472Z",
"value": [
{
"conceptId": 213026003,
"problem": "Malignant hyperpyrexia due to anesthetic",
"status": "Chronic",
"presentOnAdmission": false,
"diagnosedDateTime": null,
"inactiveDateTime": null
},
{
"conceptId": 29857009,
"problem": "Chest pain",
"status": "Acute",
"presentOnAdmission": false,
"diagnosedDateTime": null,
"inactiveDateTime": null
},
{
"conceptId": 43251000,
"problem": "Explosive acoustic trauma to ear",
"status": "Acute",
"presentOnAdmission": false,
"diagnosedDateTime": null,
"inactiveDateTime": null
}
]
}
]<?xml version="1.0"?>
<ArrayOfTimeStampedOfListOfPatientProblemListItem
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<TimeStampedOfListOfPatientProblemListItem>
<When>2017-07-10T18:53:55.3993956Z</When>
<Value>
<PatientProblemListItem>
<ConceptId>89765005</ConceptId>
<Problem>Tobacco dependence syndrome</Problem>
<Status>Chronic</Status>
<PresentOnAdmission>false</PresentOnAdmission>
<DiagnosedDateTime xsi:nil="true" />
<InactiveDateTime xsi:nil="true" />
</PatientProblemListItem>
</Value>
</TimeStampedOfListOfPatientProblemListItem>
<TimeStampedOfListOfPatientProblemListItem>
<When>2017-07-10T18:58:08.6447708Z</When>
<Value />
</TimeStampedOfListOfPatientProblemListItem>
<TimeStampedOfListOfPatientProblemListItem>
<When>2017-09-12T14:30:31.691472Z</When>
<Value>
<PatientProblemListItem>
<ConceptId>213026003</ConceptId>
<Problem>Malignant hyperpyrexia due to anesthetic</Problem>
<Status>Chronic</Status>
<PresentOnAdmission>false</PresentOnAdmission>
<DiagnosedDateTime xsi:nil="true" />
<InactiveDateTime xsi:nil="true" />
</PatientProblemListItem>
<PatientProblemListItem>
<ConceptId>29857009</ConceptId>
<Problem>Chest pain</Problem>
<Status>Acute</Status>
<PresentOnAdmission>false</PresentOnAdmission>
<DiagnosedDateTime xsi:nil="true" />
<InactiveDateTime xsi:nil="true" />
</PatientProblemListItem>
<PatientProblemListItem>
<ConceptId>43251000</ConceptId>
<Problem>Explosive acoustic trauma to ear</Problem>
<Status>Acute</Status>
<PresentOnAdmission>false</PresentOnAdmission>
<DiagnosedDateTime xsi:nil="true" />
<InactiveDateTime xsi:nil="true" />
</PatientProblemListItem>
</Value>
</TimeStampedOfListOfPatientProblemListItem>
</ArrayOfTimeStampedOfListOfPatientProblemListItem>| Property | Type |
|---|---|
| ConceptId | long (SNOMED) |
| Problem | string |
| Status | string (Acute, Chronic, Inactive) |
| PresentOnAdmission | bool |
| DiagnosedDateTime | nullable ISO8601 UTC datetime |
| InactiveDateTime | nullable ISO8601 UTC datetime |
GET GET https://server:port/api/v1/patient/{id}/smokingstatus?T1={datetime}&T2={datetime}Returns a list of objects. Each object is composed of a timestamp and a value. The value is a list of objects detailed below.
[
{
"when": "2014-06-26T17:20:15.752504Z",
"value": {
"smokingStatusCode": 266919005,
"smokingStatus": "Never A Smoker"
}
}
]<?xml version="1.0"?>
<ArrayOfTimeStampedOfPatientSmokingStatus
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<TimeStampedOfPatientSmokingStatus>
<When>2014-06-26T17:20:15.752504Z</When>
<Value>
<SmokingStatusCode>266919005</SmokingStatusCode>
<SmokingStatus>Never A Smoker</SmokingStatus>
</Value>
</TimeStampedOfPatientSmokingStatus>
</ArrayOfTimeStampedOfPatientSmokingStatus>| Property | Type |
|---|---|
| SmokingStatusCode | long (SNOMED) |
| SmokingStatus | string |
GET https://server:port/api/v1/patient/{id}/vitals?T1={datetime}&T2={datetime}Returns a list of objects. Each object is composed of a timestamp and a value. The value is a list of objects detailed below.
[
{
"when": "2015-05-05T12:00:00Z",
"value": [
{
"id": 60,
"class": "RespiratoryRate",
"performedDateTime": "2015-05-05T11:00:00Z",
"value": "28",
"units": "count per minute",
"q1": null,
"q2": null,
"q3": null
},
{
"id": 103,
"class": "Pulse",
"performedDateTime": "2015-05-05T11:00:00Z",
"value": "117",
"units": "count per minute",
"q1": "Position:Laying",
"q2": null,
"q3": null
},
{
"id": 168,
"class": "OxygenSaturation",
"performedDateTime": "2015-05-05T11:00:00Z",
"value": "95",
"units": "%",
"q1": "O2Rate:2.0",
"q2": "O2Source:Nasal Canula",
"q3": "O2 Rate Units: L/min"
},
{
"id": 61,
"class": "RespiratoryRate",
"performedDateTime": "2015-05-05T12:00:00Z",
"value": "28",
"units": "count per minute",
"q1": null,
"q2": null,
"q3": null
},
{
"id": 104,
"class": "Pulse",
"performedDateTime": "2015-05-05T12:00:00Z",
"value": "113",
"units": "count per minute",
"q1": "Position:Laying",
"q2": null,
"q3": null
},
{
"id": 169,
"class": "OxygenSaturation",
"performedDateTime": "2015-05-05T12:00:00Z",
"value": "93",
"units": "%",
"q1": "O2Rate:2.0",
"q2": "O2Source:Nasal Canula",
"q3": "O2 Rate Units: L/min"
}
]
}
]<?xml version="1.0"?>
<ArrayOfTimeStampedOfListOfVitalStatisticsData
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<TimeStampedOfListOfVitalStatisticsData>
<When>2015-07-05T05:12:00Z</When>
<Value>
<VitalStatisticsData>
<Class>RespiratoryRate</Class>
<PerformedDateTime>2015-05-05T11:00:00Z</PerformedDateTime>
<Value>28</Value>
<Units>count per minute</Units>
</VitalStatisticsData>
<VitalStatisticsData>
<Class>Pulse</Class>
<PerformedDateTime>2015-05-05T11:00:00Z</PerformedDateTime>
<Value>117</Value>
<Units>count per minute</Units>
<Q1>Position:Laying</Q1>
</VitalStatisticsData>
<VitalStatisticsData>
<Class>OxygenSaturation</Class>
<PerformedDateTime>2015-05-05T11:00:00Z</PerformedDateTime>
<Value>95</Value>
<Units>%</Units>
<Q1>O2Rate:2.0</Q1>
<Q2>O2Source:Nasal Canula</Q2>
<Q3>O2 Rate Units: L/min</Q3>
</VitalStatisticsData>
<VitalStatisticsData>
<Class>RespiratoryRate</Class>
<PerformedDateTime>2015-05-05T12:00:00Z</PerformedDateTime>
<Value>28</Value>
<Units>count per minute</Units>
</VitalStatisticsData>
<VitalStatisticsData>
<Class>Pulse</Class>
<PerformedDateTime>2015-05-05T12:00:00Z</PerformedDateTime>
<Value>113</Value>
<Units>count per minute</Units>
<Q1>Position:Laying</Q1>
</VitalStatisticsData>
<VitalStatisticsData>
<Class>OxygenSaturation</Class>
<PerformedDateTime>2015-05-05T12:00:00Z</PerformedDateTime>
<Value>93</Value>
<Units>%</Units>
<Q1>O2Rate:2.0</Q1>
<Q2>O2Source:Nasal Canula</Q2>
<Q3>O2 Rate Units: L/min</Q3>
</VitalStatisticsData>
</Value>
</TimeStampedOfListOfVitalStatisticsData>
</ArrayOfTimeStampedOfListOfVitalStatisticsData>| Property | Type |
|---|---|
| Class | string (type of vital) |
| PerformedDateTime | ISO8601 UTZ date |
| Value | string |
| Units | string |
| Q1 | optional/nullable string (qualifier 1) |
| Q2 | optional/nullable string (qualifier 2) |
| Q3 | optional/nullable string (qualifier 3) |
Note, the qualifiers are different for each class, and may contain things like position of person when taken, location on body, etc.
GET https://server:port/api/v1/patient/{id}/devices?T1={datetime}&T2={datetime}Returns a list of objects. Each object is composed of a timestamp and a value. The value is a list of objects detailed below.
[
{
"when": "2017-08-23T04:00:00Z",
"value": [
{
"id": 10,
"implantedDateTime": "2017-08-23T04:00:00Z",
"description": "Defibrillator",
"uniqueDeviceIdentifier": null,
"serialNumber": null
}
]
},
{
"when": "2017-08-24T04:00:00Z",
"value": [
{
"id": 10,
"implantedDateTime": "2017-08-23T04:00:00Z",
"description": "Defibrillator",
"uniqueDeviceIdentifier": null,
"serialNumber": null
},
{
"id": 11,
"implantedDateTime": "2017-08-24T04:00:00Z",
"description": "Coated Braided Polyester",
"uniqueDeviceIdentifier": "(01)10884521062856(11)931127(17)150707(10)A213B1(21)1234",
"serialNumber": "1234"
},
{
"id": 12,
"implantedDateTime": "2017-08-24T04:00:00Z",
"description": "Joint replacement",
"uniqueDeviceIdentifier": null,
"serialNumber": null
}
]
}
]<?xml version="1.0"?>
<ArrayOfTimeStampedOfListOfPatientDevices
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<TimeStampedOfListOfPatientDevices>
<When>2017-08-23T04:00:00Z</When>
<Value>
<PatientDevices>
<ID>10</ID>
<ImplantedDateTime>2017-08-23T04:00:00Z</ImplantedDateTime>
<Description>Defibrillator</Description>
</PatientDevices>
</Value>
</TimeStampedOfListOfPatientDevices>
<TimeStampedOfListOfPatientDevices>
<When>2017-08-24T04:00:00Z</When>
<Value>
<PatientDevices>
<ID>10</ID>
<ImplantedDateTime>2017-08-23T04:00:00Z</ImplantedDateTime>
<Description>Defibrillator</Description>
</PatientDevices>
<PatientDevices>
<ID>11</ID>
<ImplantedDateTime>2017-08-24T04:00:00Z</ImplantedDateTime>
<Description>Coated Braided Polyester</Description>
<UniqueDeviceIdentifier>(01)10884521062856(11)931127(17)150707(10)A213B1(21)1234</UniqueDeviceIdentifier>
<SerialNumber>1234</SerialNumber>
</PatientDevices>
<PatientDevices>
<ID>12</ID>
<ImplantedDateTime>2017-08-24T04:00:00Z</ImplantedDateTime>
<Description>Joint replacement</Description>
</PatientDevices>
</Value>
</TimeStampedOfListOfPatientDevices>
</ArrayOfTimeStampedOfListOfPatientDevices>| Property | Type |
|---|---|
| ID | long |
| ImplantedDateTime | ISO8601 UTC datetime |
| Description | string |
| UniqueDeviceIdentifier | string |
| SerialNumber | string |
GET https://server:port/api/v1/patient/{id}/medications?T1={datetime}&T2={datetime}Returns a list of objects. Each object is composed of a timestamp and a value. The value is a list of objects detailed below.
[
{
"when": "2015-10-21T19:05:00Z",
"value": [
{
"orderId": 163336,
"description": "insulin detemir 100 UNT/ML Injectable Solution",
"parameters": "Check BS qac and qhs or every 6 hours if NPO. If BS less than 60 then initiate Hypoglycemic protocol; 61-180 give 0 units; 181-250 give 2 units; 251-300 give 4 units; 301-350 give 6 units; 351 - 400 give 8 units; if greater than 400 then 10 units and call doctor",
"indications": null,
"rxNorm": 484322
},
{
"orderId": 162108,
"description": "Sodium Chloride 9 MG/ML Injection",
"parameters": null,
"indications": null,
"rxNorm": 1807639
}
]
},
{
"when": "2015-11-04T20:05:00Z",
"value": []
},
{
"when": "2016-01-27T19:00:00Z",
"value": [
{
"orderId": 92371,
"description": "Vancomycin 500 MG Injection",
"parameters": null,
"indications": null,
"rxNorm": 1807516
}
]
},
]<?xml version="1.0"?>
<ArrayOfTimeStampedOfListOfMedicationItem
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<TimeStampedOfListOfMedicationItem>
<When>2015-10-21T19:05:00Z</When>
<Value>
<MedicationItem>
<OrderId>163336</OrderId>
<Description>insulin detemir 100 UNT/ML Injectable Solution</Description>
<Parameters>Check BS qac and qhs or every 6 hours if NPO. If BS less than 60 then initiate Hypoglycemic protocol;61-180 give 0 units; 181-250 give 2 units; 251-300 give 4 units; 301-350 give 6 units; 351 - 400 give 8 units; if greater than 400 then 10 units and call doctor</Parameters>
<RxNorm>484322</RxNorm>
</MedicationItem>
<MedicationItem>
<OrderId>162108</OrderId>
<Description>magnesium citrate 58.2 MG/ML Oral Solution</Description>
<RxNorm>1052760</RxNorm>
</MedicationItem>
</Value>
</TimeStampedOfListOfMedicationItem>
<TimeStampedOfListOfMedicationItem>
<When>2015-11-04T20:05:00Z</When>
<Value />
</TimeStampedOfListOfMedicationItem>
</ArrayOfTimeStampedOfListOfMedicationItem>| Property | Type |
|---|---|
| OrderId | long |
| Description | string |
| Parameters | string |
| Indications | string |
| RXNorm | long |
GET https://server:port/api/v1/patient/{id}/allergies?T1={datetime}&T2={datetime}Returns a list of objects. Each object is composed of a timestamp and a value. The value is a list of objects detailed below.
[
{
"when": "2015-08-13T14:09:31.4182471Z",
"value": [
{
"id": "FDB.INGREDIENT+3675",
"rxNormCode": 723,
"allergenDescription": "Amoxicillin",
"reactions": [
{
"reactionConceptId": 39579001,
"reactionDescription": "Anaphylaxis",
"severityConceptId": 24484000,
"severityDescription": "Severe"
}
]
}
]
},
]<?xml version="1.0"?>
<ArrayOfTimeStampedOfListOfAllergenItem
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<TimeStampedOfListOfAllergenItem>
<When>2015-08-13T14:09:31.4182471Z</When>
<Value>
<AllergenItem>
<Id>FDB.INGREDIENT+3675</Id>
<RxNormCode>723</RxNormCode>
<AllergenDescription>Amoxicillin</AllergenDescription>
<Reactions>
<AllergenReaction>
<ReactionConceptId>39579001</ReactionConceptId>
<ReactionDescription>Anaphylaxis</ReactionDescription>
<SeverityConceptId>24484000</SeverityConceptId>
<SeverityDescription>Severe</SeverityDescription>
</AllergenReaction>
</Reactions>
</AllergenItem>
</Value>
</TimeStampedOfListOfAllergenItem>
</ArrayOfTimeStampedOfListOfAllergenItem>| Property | Type |
|---|---|
| Id | string |
| RxNormCode | nullable long |
| AllergenDescription | string |
| Reactions | list of objects |
| ReactionConceptId | long (SNOMED) |
| ReactionDescription | string |
| SeverityConceptId | long (SNOMED) |
| SeverityDescription | string |
GET https://server:port/api/v1/patient/{id}/labs?T1={datetime}&T2={datetime}Returns a list of objects. Each object is composed of a timestamp and a value. The value is a list of objects detailed below.
[
{
"when": "2016-12-26T07:49:00Z",
"value": [
{
"results": [
{
"resultUnit": null,
"state": "Unknown",
"resultsStandardRange": null,
"resultDescription": "MRSA DNA XXX Ql PCR",
"resultLoinc": null,
"result": "MRSA DNA XXX Ql PCR: Final\r\nSp"
}
],
"id": 4942987,
"description": "MRSA DNA XXX Ql PCR",
"orderLoinc": "35492-8",
"observationDate": "2016-12-26T07:49:00Z",
"specimenSource": "NOSE",
"specimenCondition": "HYPERCAPNIC RESPIRATORY FAILURE, ALTERED MENTAL ST"
}
]
},
{
"when": "2016-12-27T00:58:00Z",
"value": [
{
"results": [
{
"resultUnit": null,
"state": "Unknown",
"resultsStandardRange": null,
"resultDescription": "MRSA DNA XXX Ql PCR",
"resultLoinc": null,
"result": "MRSA DNA XXX Ql PCR: Final\r\nSp"
}
],
"id": 4942987,
"description": "MRSA DNA XXX Ql PCR",
"orderLoinc": "35492-8",
"observationDate": "2016-12-26T07:49:00Z",
"specimenSource": "NOSE",
"specimenCondition": "HYPERCAPNIC RESPIRATORY FAILURE, ALTERED MENTAL ST"
},
{
"results": [
{
"resultUnit": "MG/DL",
"state": "Normal",
"resultsStandardRange": "70-100",
"resultDescription": "BLOOD GLUCOSE (METER)",
"resultLoinc": null,
"result": "86.00000"
}
],
"id": 4941522,
"description": "BLOOD GLUCOSE (METER)",
"orderLoinc": null,
"observationDate": "2016-12-27T00:58:00Z",
"specimenSource": null,
"specimenCondition": "SOB"
}
]
}
]<?xml version="1.0"?>
<ArrayOfTimeStampedOfListOfLabTest GET $1:xsi="http://www.w3.org/2001/XMLSchema-instance" :xsd="http://www.w3.org/2001/XMLSchema">
<TimeStampedOfListOfLabTest>
<When>2016-12-26T07:49:00Z</When>
<Value>
<LabTest>
<Results>
<LabResult>
<State>Unknown</State>
<ResultDescription>MRSA DNA XXX Ql PCR</ResultDescription>
<Result>MRSA DNA XXX Ql PCR: Final Sp</Result>
</LabResult>
</Results>
<Id>4942987</Id>
<Description>MRSA DNA XXX Ql PCR</Description>
<OrderLoinc>35492-8</OrderLoinc>
<ObservationDate>2016-12-26T07:49:00Z</ObservationDate>
<SpecimenSource>NOSE</SpecimenSource>
<SpecimenCondition>HYPERCAPNIC RESPIRATORY FAILURE, ALTERED MENTAL ST</SpecimenCondition>
</LabTest>
</Value>
</TimeStampedOfListOfLabTest>
<TimeStampedOfListOfLabTest>
<When>2016-12-27T00:58:00Z</When>
<Value>
<LabTest>
<Results>
<LabResult>
<State>Unknown</State>
<ResultDescription>MRSA DNA XXX Ql PCR</ResultDescription>
<Result>MRSA DNA XXX Ql PCR: Final Sp</Result>
</LabResult>
</Results>
<Id>4942987</Id>
<Description>MRSA DNA XXX Ql PCR</Description>
<OrderLoinc>35492-8</OrderLoinc>
<ObservationDate>2016-12-26T07:49:00Z</ObservationDate>
<SpecimenSource>NOSE</SpecimenSource>
<SpecimenCondition>HYPERCAPNIC RESPIRATORY FAILURE, ALTERED MENTAL ST</SpecimenCondition>
</LabTest>
<LabTest>
<Results>
<LabResult>
<ResultUnit>MG/DL</ResultUnit>
<State>Normal</State>
<ResultsStandardRange>70-100</ResultsStandardRange>
<ResultDescription>BLOOD GLUCOSE (METER)</ResultDescription>
<Result>86.00000</Result>
</LabResult>
</Results>
<Id>4941522</Id>
<Description>BLOOD GLUCOSE (METER)</Description>
<ObservationDate>2016-12-27T00:58:00Z</ObservationDate>
<SpecimenCondition>SOB</SpecimenCondition>
</LabTest>
</Value>
</TimeStampedOfListOfLabTest>
</ArrayOfTimeStampedOfListOfLabTest>| Property | Type |
|---|---|
| ID | long |
| Description | string (lab test name) |
| OrderLoinc | string (LOINC) |
| ObservationDate | ISO8601 UTC date |
| SpecimenSource | string |
| SpecimenCondition | string |
| Results | list of objects |
| ResultUnit | string |
| State | string |
| ResultStandardRange | string |
| ResultDescription | string |
| Result | string |
GET https://server:port/api/v1/patient/{id}/procedures?T1={datetime}&T2={datetime}Returns a list of objects. Each object is composed of a timestamp and a value. The value is a list of objects detailed below.
[
{
"when": "2017-08-15T23:04:20.4717278Z",
"value": [
{
"procedureDate": "2017-08-15T23:04:20.4717278Z",
"conceptId": 229251002,
"notes": "Test Proc note",
"description": "Neurological gait training",
"icd10Code": "I63.9"
},
{
"procedureDate": "2017-08-15T23:04:20.4717278Z",
"conceptId": 228528009,
"notes": "Test Proc note",
"description": "Range of motion activity",
"icd10Code": "I63.9"
}
]
}
]<?xml version="1.0"?>
<ArrayOfTimeStampedOfListOfPatientProcedure
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<TimeStampedOfListOfPatientProcedure>
<When>2017-08-15T23:04:20.4717278Z</When>
<Value>
<PatientProcedure>
<ProcedureDate>2017-08-15T23:04:20.4717278Z</ProcedureDate>
<ConceptId>229251002</ConceptId>
<Notes>Test Proc note</Notes>
<Description>Neurological gait training</Description>
<Icd10Code>I63.9</Icd10Code>
</PatientProcedure>
<PatientProcedure>
<ProcedureDate>2017-08-15T23:04:20.4717278Z</ProcedureDate>
<ConceptId>228528009</ConceptId>
<Notes>Test Proc note</Notes>
<Description>Range of motion activity</Description>
<Icd10Code>I63.9</Icd10Code>
</PatientProcedure>
</Value>
</TimeStampedOfListOfPatientProcedure>
</ArrayOfTimeStampedOfListOfPatientProcedure>| Property | Type |
|---|---|
| ProcedureDate | ISO8601 UTC date |
| ConceptId | long (SNOMED) |
| Notes | string |
| Description | string |
| Icd10Code | string (ICD10) |
GET https://server:port/api/v1/patient/{id}/careteam?T1={datetime}&T2={datetime}Returns a list of objects. Each object is composed of a timestamp and a value. The value is a list of objects detailed below.
[
{
"when": "2015-07-07T12:55:38.6874766Z",
"value": [
{
"name": "Hospitalists Team",
"assignmentType": "Primary"
},
{
"name": "Hart, Bill - Hospitalists Team",
"assignmentType": "Primary"
}
]
},
{
"when": "2015-07-07T13:44:07.1312093Z",
"value": [
{
"name": "Hospitalists Team",
"assignmentType": "Primary"
},
{
"name": "Hart, Bill - Hospitalists Team",
"assignmentType": "Primary"
},
{
"name": "Bonnett, Sam - Hospitalists Team:sean",
"assignmentType": "Primary"
}
]
},
{
"when": "2015-07-20T17:01:41.3501651Z",
"value": [
{
"name": "Hospitalists Team",
"assignmentType": "Primary"
},
{
"name": "Hart, Bill - Hospitalists Team",
"assignmentType": "Primary"
},
{
"name": "Bonnett, Sam - Hospitalists Team:sean",
"assignmentType": "Primary"
},
{
"name": "Olafur, Will - Hospitalists Team",
"assignmentType": "Primary"
}
]
},
{
"when": "2015-08-05T20:34:35.5680077Z",
"value": [
{
"name": "Hospitalists Team",
"assignmentType": "Primary"
},
{
"name": "Hart, Bill - Hospitalists Team",
"assignmentType": "Primary"
},
{
"name": "Bonnett, Sam - Hospitalists Team:sean",
"assignmentType": "Primary"
},
{
"name": "Olafur, Will - Hospitalists Team",
"assignmentType": "Primary"
},
{
"name": "Bonnett, Sam - Hospitalists Team:sean",
"assignmentType": "Primary"
}
]
}
]<?xml version="1.0"?>
<ArrayOfTimeStampedOfListOfTeamAssignment
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<TimeStampedOfListOfTeamAssignment>
<When>2015-07-07T12:55:38.6874766Z</When>
<Value>
<TeamAssignment>
<Name>Hospitalists Team</Name>
<AssignmentType>Primary</AssignmentType>
</TeamAssignment>
<TeamAssignment>
<Name>Hart, Bill - Hospitalists Team</Name>
<AssignmentType>Primary</AssignmentType>
</TeamAssignment>
</Value>
</TimeStampedOfListOfTeamAssignment>
<TimeStampedOfListOfTeamAssignment>
<When>2015-07-07T13:44:07.1312093Z</When>
<Value>
<TeamAssignment>
<Name>Hospitalists Team</Name>
<AssignmentType>Primary</AssignmentType>
</TeamAssignment>
<TeamAssignment>
<Name>Hart, Bill - Hospitalists Team</Name>
<AssignmentType>Primary</AssignmentType>
</TeamAssignment>
<TeamAssignment>
<Name>Bonnett, Sam - Hospitalists Team:sean</Name>
<AssignmentType>Primary</AssignmentType>
</TeamAssignment>
</Value>
</TimeStampedOfListOfTeamAssignment>
</ArrayOfTimeStampedOfListOfTeamAssignment>| Property | Type |
|---|---|
| Name | string |
| AssignmentType | string (Primary, Consult, etc.) |
GET https://server:port/api/v1/patient/{id}/concerns?T1={datetime}&T2={datetime}Returns a list of objects. Each object is composed of a timestamp and a value. The value is a list of strings
[
{
"when": "2017-04-14T13:56:45.8381177Z",
"value": [
"This is the first Patient Question Concern."
]
},
{
"when": "2017-04-24T11:55:32.4734176Z",
"value": [
"This is the first Patient Question Concern.",
"This is the latest one! "
]
},
{
"when": "2017-04-24T11:55:57.8517082Z",
"value": [
"This is the first Patient Question Concern.",
"This is the latest one! ",
"This is my question or concern."
]
},
{
"when": "2017-04-24T12:32:38.6268387Z",
"value": [
"This is the first Patient Question Concern.",
"This is the latest one! ",
"This is my question or concern.",
"New concern"
]
}
]<?xml version="1.0"?>
<ArrayOfTimeStampedOfListOfString
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<TimeStampedOfListOfString>
<When>2017-04-14T13:56:45.8381177Z</When>
<Value>
<string>This is the first Patient Question Concern.</string>
</Value>
</TimeStampedOfListOfString>
<TimeStampedOfListOfString>
<When>2017-04-24T11:55:32.4734176Z</When>
<Value>
<string>This is the first Patient Question Concern.</string>
<string>This is the latest one! </string>
</Value>
</TimeStampedOfListOfString>
<TimeStampedOfListOfString>
<When>2017-04-24T11:55:57.8517082Z</When>
<Value>
<string>This is the first Patient Question Concern.</string>
<string>This is the latest one! </string>
<string>This is my question or concern.</string>
</Value>
</TimeStampedOfListOfString>
</ArrayOfTimeStampedOfListOfString>| Property | Type |
|---|---|
| value | list of strings |
GET https://server:port/api/v1/patient/{id}/assessments?T1={datetime}&T2={datetime}Returns a list of objects. Each object is composed of a timestamp and a value. The value is a list of objects detailed below.
[
{
"when": "2017-05-12T15:02:07.9783585Z",
"value": [
{
"plan": "this is our plan",
"hpi": "test HPI"
}
]
},
{
"when": "2017-05-12T15:20:52.8961439Z",
"value": [
{
"plan": "this is our plan",
"hpi": "test HPI"
},
{
"plan": null,
"hpi": null
}
]
},
{
"when": "2017-05-15T14:13:40.1691791Z",
"value": [
{
"plan": "this is our plan",
"hpi": "test HPI"
},
{
"plan": null,
"hpi": null
},
{
"plan": "Plan",
"hpi": "This is the plan"
}
]
}
]<?xml version="1.0"?>
<ArrayOfTimeStampedOfListOfAssessment
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<TimeStampedOfListOfAssessment>
<When>2017-05-12T15:02:07.9783585Z</When>
<Value>
<Assessment>
<Plan>this is our plan</Plan>
<HPI>test HPI</HPI>
</Assessment>
</Value>
</TimeStampedOfListOfAssessment>
<TimeStampedOfListOfAssessment>
<When>2017-05-12T15:20:52.8961439Z</When>
<Value>
<Assessment>
<Plan>this is our plan</Plan>
<HPI>test HPI</HPI>
</Assessment>
<Assessment />
</Value>
</TimeStampedOfListOfAssessment>
<TimeStampedOfListOfAssessment>
<When>2017-05-15T14:13:40.1691791Z</When>
<Value>
<Assessment>
<Plan>this is our plan</Plan>
<HPI>test HPI</HPI>
</Assessment>
<Assessment />
<Assessment>
<Plan>Plan2</Plan>
<HPI>HPI2</HPI>
</Assessment>
</Value>
</TimeStampedOfListOfAssessment>
</ArrayOfTimeStampedOfListOfAssessment>| Property | Type |
|---|---|
| Plan | string |
| HPI | string |
GET https://server:port/api/v1/patient/{id}/goals?T1={datetime}&T2={datetime}Returns a list of objects. Each object is composed of a timestamp and a value. The value is a list of strings.
<?xml version="1.0"?>
<ArrayOfTimeStampedOfListOfString
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<TimeStampedOfListOfString>
<When>2017-07-11T12:49:19.5171381Z</When>
<Value>
<string>Big Goal</string>
</Value>
</TimeStampedOfListOfString>
</ArrayOfTimeStampedOfListOfString>| Property | Type |
|---|---|
| Value | list of strings |
GET https://server:port/api/v1/patient/{id}/immunizations?T1={datetime}&T2={datetime}Returns a list of objects. Each object is composed of a timestamp and a value. The value is a list of objects detailed below.
[
{
"when": "2017-08-04T04:00:00Z",
"value": [
{
"vaccineDescription": "hepatitis B vaccine, unspecified formulation",
"vaccineType": "Vaccine",
"cvxCode": 12345
},
{
"vaccineDescription": "measles, mumps and rubella virus vaccine",
"vaccineType": "Titer",
"cvxCode": 12425
}
]
}
]<?xml version="1.0"?>
<ArrayOfTimeStampedOfListOfVaccineItem
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<TimeStampedOfListOfVaccineItem>
<When>2017-08-04T04:00:00Z</When>
<Value>
<VaccineItem>
<VaccineDescription>hepatitis B vaccine, unspecified formulation</VaccineDescription>
<VaccineType>Vaccine</VaccineType>
<CVXCode>1234</CVXCode>
</VaccineItem>
<VaccineItem>
<VaccineDescription>measles, mumps and rubella virus vaccine</VaccineDescription>
<VaccineType>Titer</VaccineType>
<CVXCode>12344</CVXCode>
</VaccineItem>
</Value>
</TimeStampedOfListOfVaccineItem>
</ArrayOfTimeStampedOfListOfVaccineItem>| Property | Type |
|---|---|
| VaccineDescription | string |
| VaccineType | string |
| CVXCode | long (CVX) |
GET https://server:port/api/v1/patient/{id}/ccda?T1={datetime}&T2={datetime}The T1 and T2 parameters in this requests are a bit different than the usual ones.
If T1 and T2 are both missing, we will get the users most recent admission and return the CCDA for that visit. If T1 is given by itself, that is used as a starting date, and all admissions from that date forward are used. Providing just T2 will find all admissions that occured before T2. Provinding both will act as the others do and it will find all admissions between the two dates.
Returns all of the data categories specified in the Common Clinical Data Set at one time in a summary record formatted according to the Consolidated CDA Release 2.1 Continuity of Care Document (CCD) template. If no record is found, an error message (encoded as xml) or possibly an empty string will be returned.
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type='text/xsl' href='CDA.xsl'?>
<ClinicalDocument xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:sdtc="urn:hl7-org:sdtc" classCode="DOCCLIN" moodCode="EVN" xmlns="urn:hl7-org:v3">
<realmCode code="US" />
<typeId root="2.16.840.1.113883.1.3" extension="POCD_HD000040" />
<templateId root="2.16.840.1.113883.10.20.22.1.1" />
<templateId root="2.16.840.1.113883.10.20.22.1.2" />
<templateId root="2.16.840.1.113883.10.20.22.1.1" extension="2015-08-01" />
<templateId root="2.16.840.1.113883.10.20.22.1.2" extension="2015-08-01" />
<templateId root="2.16.840.1.113883.10.20.22.1.4" extension="2014-06-09" />
<templateId root="2.16.840.1.113883.3.3251.1.1" assigningAuthorityName="HL7 Security" />
<id root="2.16.840.1.113883.3.2700.2.2.1" extension="CERT-B1-INP2-V14" />
<code codeSystem="2.16.840.1.113883.6.1" codeSystemName="LOINC" code="34133-9" displayName="Summarization Of Episode Note" />
<title>Health Summary</title>
...
</ClinicalDocument>See CCDA 2.1 specs for details.
MedOne Systems, LLC. owns and operates this set of Application Programming Interfaces (API) (such APIs shall hereinafter be referred to individually and collectively as the “MedOne Systems API”). The MedOne Systems API is made available to Eligible Applications, as defined herein, on behalf of an Authorizing Practitioner or Authorizing System, as defined herein, under the following terms and conditions (the “Terms of Use”).
MedOne Systems API: The MedOne Systems API is an Internet service offered by MedOne Systems to provide third-party applications with access to health information. The MedOne Systems API provides a means by which, on behalf of a practitioner, or system, applications may securely access select portions of health information. Each third-party application will provide credentials to access such information. When accessing data on behalf of a patient or practitioner, third-party applications will obtain authentication and authorization from either the practitioner or system.
The MedOne Systems API is the intellectual property of MedOne Systems and no part of the MedOne Systems API may be reproduced without first obtaining MedOne System’s written permission. The information and services provided on or through the MedOne Systems API may be updated or removed at any time without notice.
Eligible Application: An Eligible Application shall be defined as an application that i) agrees to these Terms of Use without modification; ii) has been approved by an MedOne Systems API System Administrator; and iii) has received client credentials from a MedOne Systems API authorization server. If you meet the definition of an Eligible Application, by using a MedOne Systems API, you represent and warrant that you are an Eligible Application. Subject to these Terms of Use, MedOne Systems hereby grants to Eligible Applications a non-exclusive, non-transferable right to access and use the MedOne Systems API.
Authorizing Practitioner: An Authorizing Practitioner shall be defined as a practitioner that i) agrees to these Terms of Use without modification; ii) is 18 years of age or older; and iii) has received access credentials for a MedOne Systems system. If you meet the definition of an Authorizing Provider, by using a MedOne Systems API, you represent and warrant that you are an Authorizing Practitioner. Subject to these Terms of Use, MedOne Systems hereby grants to Authorizing Practitioners a non-exclusive, non-transferable right to access and use the MedOne Systems API.
Authorizing System: An Authorizing System shall be defined as an electronic system whose controlling interest, developing organization, or maintaining alliance i) agrees to these Terms of Use without modification; ii) is legally able to access health information under the constraints of HIPAA; and iii) has received access credentials for a MedOne Systems system. If you meet the definition of an Authorizing System, by using a MedOne Systems API, you represent and warrant that you are capable of representing the Authorizing System. Subject to these Terms of Use, MedOne Systems hereby grants to Authorizing Systems a non-exclusive, non-transferable right to access and use the MedOne Systems API.
Use of the MedOne Systems API: Use of the MedOne Systems API by an Eligible Application is contingent upon the application’s custodian’s agreement to i) use the MedOne Systems API solely as permitted by these Terms of Use; ii) use the MedOne Systems API only to access information on behalf of Authorizing Practitioners, or an Authorizing System; iii) use the MedOne Systems API in accordance with HIPAA Rules; iv) not impersonate or attempt to impersonate someone else; v) not use the MedOne Systems API to defame, abuse, harass, stalk, threaten, damage the reputation of or otherwise infringe on the legal rights of others; vi) not use the MedOne Systems API in any way that would infringe on the intellectual property rights of MedOne Systems or any third party; vii) not use the MedOne Systems API in any way that would violate the privacy of any third party; viii) not use the MedOne Systems API to disseminate any information that, in MedOne Systems’ sole discretion, is inappropriate, profane, defamatory, infringing, obscene, offensive, indecent, or illegal; ix) not intentionally post inaccurate, false or misleading information; x) not use the MedOne Systems API in any way that is unlawful; xi) not use the MedOne Systems API in any way that would adversely affect the availability or efficiency of the MedOne Systems API or interfere with any other Eligible Application’s ability to access and use the MedOne Systems API; xii) not attempt to defeat or evade any security or access control of the MedOne Systems API; xiii) protect the security of and not share with any third party any user name, authorization, login and password information used to access the MedOne Systems API; and xiv) not to allow any third party acting on your behalf to act in any manner not allowed by these Terms of Use.
Assumption of Risk: By being an Authorizing Practitioner, or Authorizing System, you are assuming certain risks that include (but are not limited to) i) personal health information may be disclosed to unauthorized individuals if a password is stolen or shared or if a computer logged into an account associated with the MedOne Systems API is left unattended; ii) personal health information may be disclosed to unauthorized individuals subsequent to downstream electronic transmission via an Eligible Application; and iii) information available through the MedOne Systems API may be incomplete, inaccurate, corrupted, delayed or otherwise not delivered.
Termination of Access and Use: MedOne Systems may, in its sole discretion, terminate the right to access and use the MedOne Systems API of any Eligible Application that has violated these Terms and Conditions.
No License: Nothing in these Terms of Use is intended to grant any license or any other rights to the MedOne Systems API, except as expressly set forth herein, or transfer any rights, title or interests in or to any intellectual property of MedOne Systems.
Third Party Links: The MedOne Systems API and/or its documentation may include links to other third party sites to provide access to additional information; however these Terms of Use do not apply to any third party sites that may be linked via the MedOne Systems API or in its documentation. MedOne System is not responsible or liable for the content or use of the linked sites. MedOne Systems recommends that you review the terms of use of any third party site you may visit via a link via the MedOne Systems API or in its documentation.
Security: MedOne Systems employs appropriate security measures to protect against unauthorized access. Such security measures include reasonable and appropriate technical, physical and administrative controls. While MedOne Systems takes steps to mitigate security risks, it must be understood that there are security risks inherent to use of the Internet that are outside of MedOne System’s ability to control and MedOne Systems cannot guarantee absolute safety from intrusion. Individuals who use the MedOne Systems API should do their part to protect their personal information by safeguarding passwords and logging off completely when finished using the MedOne Systems API.
Disclaimers: THE MEDONE SYSTEMS API IS PROVIDED “AS IS” AND “AS AVAILABLE” WITHOUT WARRANTY OF ANY KIND. MEDONE SYSTEMS MAKES NO REPRESENTATIONS AS TO THE SUITABILITY, RELIABILITY, AVAILABILITY, TIMELINESS AND ACCURACY OF INFORMATION AND SERVICES PROVIDED ON OR THROUGH MEDONE SYSTEMS WEBSITE. MEDONE SYSTEMS HEREBY DISCLAIMS ALL WARRANTIES WITH REGARD TO THE MEDONE SYSTEMS API, INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. MEDONE SYSTEMS DOES NOT WARRANT THAT THIS SITE, ITS SERVERS, EMAIL, OR OTHER ELECTRONIC TRANSMISSIONS SENT VIA THE MEDONE SYSTEMS API WILL BE FREE OF VIRUSES OR ANY OTHER HARMFUL COMPONENTS.
TO THE FULLEST EXTENT PERMITTED BY LAW, IN NO EVENT SHALL MEDONE SYSTEMS, ITS OFFICERS, DIRECTORS, EMPLOYEES AND AGENTS, BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR ANY OTHER DAMAGES WHATSOEVER RESULTING FROM OR IN ANY WAY CONNECTED TO THE USE, PERFORMANCE OR AVAILABILITY OF THE MEDONE SYSTEMS API, EVEN IF MEDONE SYSTEMS HAS BEEN NOTIFIED OF THE POSSIBILITY OR LIKELIHOOD OF SUCH DAMAGES OCCURRING, AND WHETHER SUCH LIABILITY IS BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY, PRODUCTS LIABILITY OR OTHERWISE.
YOU ACKNOWLEDGE AND AGREE THAT YOUR USE OF THE MEDONE SYSTEMS API IS AT YOUR SOLE RISK AND YOUR SOLE AND EXCLUSIVE REMEDY FOR ANY INJURY YOU MAY SUFFER RELATED TO OR ARISING FROM YOUR USE OF, OR INABILITY TO USE, THE MEDONE SYSTEMS API OR ANY DISSATISFACTION YOU MAY HAVE WITH THESE TERMS AND CONDITIONS IS TO DISCONTINUE USING THE MEDONE SYSTEMS API.
Indemnification: By using the MedOne Systems API, you agree to indemnify, defend and hold harmless MedOne Systems, its officers, directors, employees and agents, from and against all claims liabilities, losses, expenses, damages and costs resulting from your use of the MedOne Systems API or any violation of these Terms of Use.
Terms of Use Changes: These Terms of Use may be revised by MedOne Systems from time to time. When any revisions are made, the revised Terms of Use will be posted to the MedOne Systems API and will be effective as of the date of the last update provided at the bottom of the web page. As these Terms of Use can be updated at any time, MedOne Systems recommends that you review this web page regularly.
Acceptance of the Terms of Use: Use of the MedOne Systems API signifies your acknowledgement and acceptance of these Terms of Use. If you do not agree to the terms of these Terms of Use, please do not use the MedOne Systems API.
General: If any portion of these Terms of Use is ruled by a court of competent jurisdiction to be contrary to applicable law, the affected provision(s) shall be changed so as to be valid, enforceable and interpreted to most closely match the objectives of the origin provision(s).
No failure or delay by MedOne Systems in exercising any right, power or remedy under these Terms of User shall be construed as a waiver of any such right, power or remedy.
These Terms of Use may not be modified, amended or waived except as may be adopted by MedOne Systems in writing.
Last modified: September 30, 2017