This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Issues for EMS Project"
Jump to navigation
Jump to search
| (9 intermediate revisions by the same user not shown) | |||
| Line 9: | Line 9: | ||
|width="200pt"| Status | |width="200pt"| Status | ||
|- | |- | ||
| − | |Is the automated collision notification information included in a run report? || | + | |Is the automated collision notification information included in a run report? || Deferred; specific report requirements will be defined. || Open, 2/10/11; closed 6/13/11 |
|- | |- | ||
| − | |Is specialtyCareProviderTypeCode inferrable from Crew, or is it different information? || | + | |Is specialtyCareProviderTypeCode inferrable from Crew, or is it different information? || Operating assumption: no; it's a different element. || Open, 2/10/11; closed 6/13/11 |
|- | |- | ||
| − | |Can "medicalNecessityCertificationIndicator" be derived from certification object instance? || || Open, 2/10/11 | + | |Can "medicalNecessityCertificationIndicator" be derived from certification object instance? || Operating assumption: irrespective, we'll record it. || Open, 2/10/11; closed 6/13/11 |
| + | |- | ||
| + | |What is the significance of the 'review requested'? || || Open, 2/10/11 | ||
| + | |- | ||
| + | |What would be more useful in the header, Service Request Type or Complaint Code? || Service. Complaint's not unique || Open, 2/10/11; closed 6/17 | ||
| + | |- | ||
| + | |What are implications of overlap between EArrest.03 & EArrest.09? || they overlap; may be business rules in application || Open, 6/13/11; closed 6/17 | ||
| + | |- | ||
| + | |Confirm EOther.05 is a classification and does not imply intent. || true || closed 6/17 | ||
| + | |- | ||
| + | |Complaint model || many complaints, one of which may be chief. Impression is for patient and may be based on many complaintes. || closed 6/17 | ||
| + | |- | ||
| + | |AED without defibrillation? || yes: AED does not always detect a shockable rythm || Closed 6/17 | ||
| + | |- | ||
| + | |complaint relation to disaster type (e.g., exclusive?) || none. Both are OK. || Closed 6/17 | ||
| + | |- | ||
| + | |Coding strength || CNE || Closed 6/17 | ||
| + | |- | ||
| + | |EDevice.02 Device Event name--need to split these? (some observations, some procedures: heart rate, power on, defibrillation) || for consistency with other concepts, no. correct? || Open 6/17 | ||
| + | |- | ||
| + | |"No anticoagulants or bleeding disorder" seems to mean "No anticoagulants" in the Med question (EHistory.14) and "No bleeding disorder" in the history question (EHistory.10). I could answer "no anticoagulants" for the one, but still record a "bleeding disorder" for the other. True? || || Open 6/18 | ||
| + | |- | ||
| + | |See Jan 26 minutes regarding Route of Administration semantics || See Jan 26 minutes: use FDA; model devices separately; add 'intraosseous' || Closed 1/26/12 | ||
|} | |} | ||
Latest revision as of 15:21, 9 February 2012
Questions regarding the EMS project
Back to EMS DAM page
| Question | Answer | Status |
| Is the automated collision notification information included in a run report? | Deferred; specific report requirements will be defined. | Open, 2/10/11; closed 6/13/11 |
| Is specialtyCareProviderTypeCode inferrable from Crew, or is it different information? | Operating assumption: no; it's a different element. | Open, 2/10/11; closed 6/13/11 |
| Can "medicalNecessityCertificationIndicator" be derived from certification object instance? | Operating assumption: irrespective, we'll record it. | Open, 2/10/11; closed 6/13/11 |
| What is the significance of the 'review requested'? | Open, 2/10/11 | |
| What would be more useful in the header, Service Request Type or Complaint Code? | Service. Complaint's not unique | Open, 2/10/11; closed 6/17 |
| What are implications of overlap between EArrest.03 & EArrest.09? | they overlap; may be business rules in application | Open, 6/13/11; closed 6/17 |
| Confirm EOther.05 is a classification and does not imply intent. | true | closed 6/17 |
| Complaint model | many complaints, one of which may be chief. Impression is for patient and may be based on many complaintes. | closed 6/17 |
| AED without defibrillation? | yes: AED does not always detect a shockable rythm | Closed 6/17 |
| complaint relation to disaster type (e.g., exclusive?) | none. Both are OK. | Closed 6/17 |
| Coding strength | CNE | Closed 6/17 |
| EDevice.02 Device Event name--need to split these? (some observations, some procedures: heart rate, power on, defibrillation) | for consistency with other concepts, no. correct? | Open 6/17 |
| "No anticoagulants or bleeding disorder" seems to mean "No anticoagulants" in the Med question (EHistory.14) and "No bleeding disorder" in the history question (EHistory.10). I could answer "no anticoagulants" for the one, but still record a "bleeding disorder" for the other. True? | Open 6/18 | |
| See Jan 26 minutes regarding Route of Administration semantics | See Jan 26 minutes: use FDA; model devices separately; add 'intraosseous' | Closed 1/26/12 |
