Comments (1)
Thank you @bilhar97! I've created a PR with commits for many of these items.
What is left for discussion after the review of the changes to address the rest:
-
- Section 7.4 Do we need a use case for updating an existing device-patient association?
-
- Paragraph 760 (in original PCIM spec, carried over into Foundational spec). Is this section still relevant as is? Not sure what this means in the context of the new PCIM?
“A device association can be reported as a point-in-time event, in which case a separate disassociate message is not required to delineate the end of the association. Alternatively, the association event message can convey a duration during which the association was in effect. The latter is equivalent to an associate/disassociate message pair and may be preferable for short duration associations (e.g., spot vitals collection).”
- Paragraph 760 (in original PCIM spec, carried over into Foundational spec). Is this section still relevant as is? Not sure what this means in the context of the new PCIM?
from dev.pcim.
Related Issues (20)
- Feedback items July 23rd Al Engelbert
- [Topic] Rules around Accepting DEV-51
- Add text to define/describe application ack between DPAM and DPAR
- ORU_R01 reference feedback item
- Merge CP #4 (error codes) into CP #1 (foundational) HOT 4
- Review of latest PCIM Foundational CP
- 9/26/2023 Feedback
- Should the application ack between manager and consume have its own message type? HOT 1
- Review of Latest PCIM Foundational Spec - Comments HOT 2
- [WG] Define MEMDMC -> PCIM interface for device registration
- [WG] Specify whether DPAR connection to DPAM can be used for application ACK or if new connection back is required
- [CAT24] PRT 4.3 - Name of coding system, should this be required in spec
- [CAT24] Define a new message template due to PRT segments included after OBX segments
- [CAT24] Update DPAM->DPAC test, make it optional if DEV-19 is not supported
- Allow manager to send DEV-52 messages to consumer over a DEV-19 initiated persistent connection
- Add optional FHIR interface to manager and additional client actor to support retrospective queries
- Use OBR.3 and OBR.29 to identify device association for any action (association, disassociate, correction, wrong, update) in DEV-52 messages
- Move PCIM to HL7 version 2.8.2 or later?
- Clear Actor agreement on EQUIP PRT.10 semantics / encoding rules (serial number, per device eui-64, uuid, ...)
- Extensions for additional attributes at time of association, such as order ID, channel #, etc.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dev.pcim.