Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feedback items July 23rd Al Engelbert #51

Closed
eldonmetz opened this issue Jul 27, 2023 · 0 comments
Closed

Feedback items July 23rd Al Engelbert #51

eldonmetz opened this issue Jul 27, 2023 · 0 comments

Comments

@eldonmetz
Copy link
Collaborator

eldonmetz commented Jul 27, 2023

· Section 3.52.4.1, 2nd sentence should have some indication that only those messages that meet the filter criteria, if specified, will be sent

· Section 3.19, 3rd paragraph: The sentence beginning with "If the DEV-19 transaction is not supported, ..." doesn't make sense to me, especially the reference to "...and the network connection is lost".

o Is the original intent of this to say that if the manager doesn't support DEV-19 then it should just become a normal feed of all associations?

· Contradiction:
o Table 3.52.2-1, Actor Roles, Device-Patient Association Consumer: "The consumer initially receives current association status followed by updates in realtime on a connection established by the Manager. It may optionally send a filter dynamically in the form a HL7 query or that filter may be pre-configured.
§ This makes it sound like the filter is sent on the connection that was established from the Manager to the Consumer

o Section 3.19.4.1.3, Expected Actions, 2nd paragraph: "one practical method is for the Device-Patient Association Manager to maintain an open TCP listen port to accepts connections from one or more Device- Patient Association Consumer clients and then to open an individual TCP connection with each requester that persists as long as the client is connected and the query is valid"

· Inconsistency:
o Section A.1 uses "Communicate Device-Patient Association and Disassociation"

o Table A.1.1-1 uses "Report Device Patient Association", and text below the table uses "Communicate Device-Patient Association" and "Report Device-Patient Association"

· Section A.1.2.5, "OBX - Observation (for Patient ID)": the section name is confusing, as the OBX isn't used to identify the patient involved

· Table A.1.2.5-1, field 3, Description column: should not be MDCX

· PRT-10 Participation Device (EI), paragraph 1, something is missing near the end: "...but in any case must contain See details in the"

· Section A.2.3.2, "QPD Segment": what is CSC data type? Should this be QSC?

· Section A.2.4, RCP Segment: "RCP-4 Execution and Delivery Time is required when RCP-1 contains the value of RCP-1 D (Deferred)."

o The second RCP-1 should not be present

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant